Has anyone noticed the reports not outputting Constraint Report? #46
-
|
So question, has anyone noticed that with a new model you are not getting the Constraint report output? Not sure if this is a new issue or not so wanted to ask here first. Some of my older ORM files are generating the report fine. So it might be a file issue but not sure if it is just me.
I think there might be a bad format or bug in the report generation but wanted to check before creating the issue. The rest of the application seems to be operating as expected so I don't think the file itself is bad. Just that it is not generating. I even simplified down to a single Object, 2 value types and 2 binary roles. This is also failing to generate a report at all.
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
Wow, based on the code this has never worked due to the simplicity of the model. The generator uses either a filtered list or the 'all' list of object types and fact types. The failure is trying to sort the 'all' list, which isn't editable without copying the contents out. You don't need anything special for a filtered model: any spanning uniqueness constraint, explicit objectification or unary fact type will put you in a filtered state. The vast majority of models have at least one of these elements. This is fixed in NORMA 1.0.3049.1. If you have automatic updates on you'll get the updated version by restarting Visual Studio. Thanks for the report. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome... Thanks for the quick check. I thought I was losing my mind or did something wrong to my files. LOL. Make more sense now that you explained. |
Beta Was this translation helpful? Give feedback.
-
|
Confirmed that everything generated. Thanks again.
|
Beta Was this translation helpful? Give feedback.
-
|
Don't worry, I thought you were losing your mind as well when I first read the report :) Then I thought I'd broken something adding the Word Report in Pro, but that didn't change anything anywhere near this code. Anyway, easy fix. I actually deleted a few lines or code. |
Beta Was this translation helpful? Give feedback.
Wow, based on the code this has never worked due to the simplicity of the model. The generator uses either a filtered list or the 'all' list of object types and fact types. The failure is trying to sort the 'all' list, which isn't editable without copying the contents out. You don't need anything special for a filtered model: any spanning uniqueness constraint, explicit objectification or unary fact type will put you in a filtered state. The vast majority of models have at least one of these elements.
This is fixed in NORMA 1.0.3049.1. If you have automatic updates on you'll get the updated version by restarting Visual Studio.
Thanks for the report.