Overview
Among the new functionalities in release 6.6, there is one in particular that I want to bring to your attention as it is currently not working as expected.
In 6.6, Report Auto Gen Level option has been introduced as new feature. Please find below the details for Auto Gen Level and Report Auto Gen Level:
Auto Gen Level
Displays an option indicating if and how tables, views and stored procedures are autogenerated.
Values are:
New Rules – Alter Table and Build New Views and Stored Procedures Only – When autogenerating, a table is updated and only new views and stored procedures are created. Existing views and stored procedures are not updated.
Off – No Generating Any SQL Objects – AutoGen is not used.
NOTE: Rules for mappings with the Copy, Default, Rule, XRef, and Xref actions are not built. For mappings with the Construction action (i.e., mappings that use Enhanced Construction), the table and field are not created in the target database and a page is not created in Construct. Full Construction objects are built via the Sync in Target Design. The rules must be generated on the Automation SQL Field Mappings page.
On – Drop & Rebuild Table, Views and Stored Procedures - Any SQL objects previously created for the target are dropped and a new table, SQL views and stored procedures with the same name are added.
Rebuild – Alter Table and Drop & Rebuild Views And Stored Procedures – The table is updated. Views and stored procedures previously created for the target are dropped and new SQL views and stored procedures with the same name are added.
Report Auto Gen Level
Displays an option indicating if and how business user reports are generated for the target with SQL AutoGen.
Options are:
On - Drop & Rebuild Report Views and Registrations. Any SQL views previously created for the business user reports in the target are dropped and new SQL views with the same name are added.
Off - No Report Generation. AutoGen is not used.
New - Add new reports without modifying existing report views or registrations. When autogenerating, only new views are created. Existing views are not updated.
Considerations
In 6.6.0
In this release, the Report Auto Gen Level was introduced for first time but it was not working as expected. Accordingly to the documentation, when you select New, only new views are created but in reality all reports were updated. There was a ticket for this issue and it was quickly resolved.
Workaround: Upgrade to 6.6.1.
In 6.6.1
For this release, Report Auto Gen Level is affecting the creation of Source and Target rules. When you chose the option New, Source and Target rules are not dropped and therefore, are not updated. In case that you change a mapping and you have Report Auto Gen Level = New, when you click on Create All rules, the rules are not dropped (and therefore not re-created), so will keep the old version of the mapping.
Essentially this is equivalent (except for the new rules) to say that by setting Report Auto Gen Level = New, you are using Auto Gen Level = Off.
There is a ticket open and Development team is working on it:
[DSP-9560] - Common: 6.6.1 AE Instructions won't drop Source/Target Rules when [Report Auto Gen Level] is set to "New Reports”
Workaround: Before click on Create All Rules, ensure that Report Auto Gen Level = On.
Details of the issue:
1. Create a source/target mapping.
2. Build the rule
If the rule does not exist, then, there is not issue. When you click on Build, the rule gets created:
3. Reset the mapping. This action removes the rule from Transform (this depend on your local configuration). Notice that the view still exists in SQL Server.
4. Create a new mapping.
5. Build the rule. You can see that is created with default value 402 (before 403) at 12.52h.
But in SQL you still has the old view:
Your mapping says 402 but your view 403.
6. To fix that, you have to change Report Auto Gen Level = On
7. Now, when you click either build the rule or Create All Rules, DSP drops it and create it again.
Remember to change it back to Report Auto Gen Level = New if you want to protect your reports to be re-generated.
I hope you find this post interesting and useful.
Please do not hesitate to ask any questions.
Comments
0 comments