on 11-18-2015 8:35 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
the only way is you have to deselect it manually before exporting to repository for the first time.
Thanks,
Venkat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Michael,
Reason behind "Retrieve duplicate rows" being checked by default, could be:
- Unchecking the option will put DISTINCT (or GROUP BY) in the SQL which could affect the query performance and can be time consuming.
- In actual scenarios, it is suggested not to use DISTINCT and check if query is giving duplicate records.
If the SQL is giving duplicate records that means the schema at universe level need to be checked and few joins might be missing.
By using DISTINCT, it will firstly hamper the performance and you will not be able to check whether the SQL generated is correct and optimized.
Regards,
Yuvraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I am not very sure if you can uncheck this option for default.This is the standard behaviour.but you can try one option to create one template for particular universe and unchecked this option.
For all new reports use only template to create reports.in this every time this option will be unchecked default for all new reports.
Amit
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.