Analytics Common mistakes to avoid in SAP Cloud Applications Studio
Here i would document some of the common mistakes made during editing Analytics objects from SDK:
1) Do not edit Analytical objects like Report , Key figure etc directly in the Key user tool (Business Analytics Work center)
Edit the analytical objects like Report by launching it from SDK and not directly from key user tool i,e by logging into the Application UI and then accessing Business Analytics Work center and then editing the analytical objects, the reason is SDK won’t be able to capture the changes made direcly in the key user tool.
Ex: Login to the Application UI, select Business Analytics Work centre, select Report created from SDK , add Report View ,this is incorrect, since the change was made by logging into the Application UI , SDK won’t capture the changes, hence, the changes won’t be visible when we upload this solution in some other tenant
Correct sequence is: Login in to SDK, open the solution, double click on the Report, add Report View Now, SDK would caputure the changes, and this change would be reflected in any tenant where you upload the solution
2) Key user tool (KUT) created extension field in Analytical objects like Joined datasource
KUT created extension field is available only locally in the current tenant only, so if you upload such a solution into other tenant, activation of the object will fail , since the KUT created extension field won’t be available in the target tenant.
To avoid such issue, make sure the KUT created extension field is available in the target tenant before you upload the solution into the target tenant.
Ex: Created an extension field in the key user tool and used it in joined datasource, uploading of this solution into another tenant fails since the key user created extension field won’t be available in the target tenant