Users are able to see shared One View reports (OVR) but they unable to create custom OVRs. What is the type of security needed for creating custom OVRs?
Ha! This question is a real head-scratcher. I bet the developers who came up with these security options had a good laugh. Anyway, my money's on D) View security - it just seems like the most logical choice here.
This is a tricky one! I'm leaning towards D) View security, but I'm also wondering if E) Content security might be the answer. After all, the content of the reports is what users are interacting with, right? *scratches head*
I'm not too familiar with One View reports, but based on the options, I think the answer is D) View security. It makes sense that creating custom reports would require specific view-level permissions.
Hmm, this seems to be a question about security permissions for creating custom OVRs. I'm guessing the answer is D) View security, since that's the type of security that governs what users can see and do with specific views.
Yvonne
1 months agoLawrence
9 days agoArlene
17 days agoCarole
19 days agoLeah
1 months agoFiliberto
1 months agoJohnetta
3 days agoEliz
5 days agoHeike
15 days agoGarry
2 months agoAngelo
1 months agoLea
1 months agoGianna
2 months agoRashad
2 months agoPaz
2 months agoGearldine
3 months ago