Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture
Comments
-
Hi Experts, we are facing the same both in OACS stand alone and FDI. Can anyone please help with response?
-
Thank you ! Appreciated !
-
Upvoted ! Thanks. This is a much required feature.
-
Excellent idea Swetha! for better and comfortable user experience !
-
We need the same, excel export (for entire OACS / FDI workbook with all canvases) with different canvases as different sheets in an excel workbook. Looking forward for inputs from experts. Thanks!
-
Hi, The following should be followed from the Day 1 of project implementation and should be followed during entire project life cycle to avoid such scenario at the first place. Using catalogue (Folder-Level Restrictions) Permissions judiciously. Restricting Admin / Author privilege to only few users with proper training…
-
No this behavior is not changed in FDI. OOTB content or its permissions can not be amended even now.
-
Hi Anurag, please refer to this discussion thread which I referred few months back for our project requirement: https://community.oracle.com/products/oracleanalytics/discussion/22352/fdi-how-to-hide-restrict-access-to-oracle-folder-under-catalog-shared-folder
-
Hi Any solution to this problem yet? We are facing the similar issue.
-
Hi Abhishek, I crossed checked few of the Workforce related subject areas, but could not find. Are you looking for this field in any particular OTBI subject area?
-
Hi @SaurabhJaiswal-Oracle Can you please refer the following doc ids, Doc ID 2791599.1 Doc ID 2609004.1 Few points from these docs are already mentioned by few members, but can you please ensure all the points mentioned in the doc are followed.
-
Hi @SiddharthDang-Oracle The problematic agent which is currently being tested by the user, is present in his "My Folder". Hence no other user can schedule the same other than him. Regards, Ram
-
Hi @Anirban Basu-133546 /@SiddharthDang-Oracle We tried these options already and did not work. Surprisingly only one user is facing this issue while running agents, no other use is facing this. Hence, it looks like no other agent runs in the background when the particular user gets the error.