Hello all,
I have created a hybrid workflow for my company that allows us to use an office-based survey to massively lighten the load on our field teams when it comes to data collection. This is accomplished through the pulldata(@layer) function. Programmatically, the system works entirely as expected and is able to source the correct data for different asset classes as needed.
However, it appears that the only members of our AGOL Organization that can actually fully utilize this functionality are those with the 'Administrator' role type. I have checked and rechecked that the feature layer being queried with pulldata() is shared with all relevant folks, and in fact a call with Esri Tech Support yesterday produced no meaningful changes to any settings regarding my survey data, and I am now waiting for more nuanced answers from an internal team.
This morning, I have been on the phone with a handful of our field techs to experiment what changing their role types would do. These are all people whose user type is 'Standard' and whose roles are all the default 'User'. I tried changing them one by one to all other user roles, and consistently the only user role that can make use of the pulldata() functionality is Administrator.
I don't understand why this is the case, and the Esri folks I have spoken with so far don't seem to either. Having an AGOL Org that is completely composed of Administrators seems to defeat the entire purpose of having any discretion in assigning user roles, and I have to believe there is a way to enable my field teams to use the system I have created.
Has anyone else had success in managing the permissions/privileges necessary to enable an average field worker to make use of pulldata(@layer) and pulldata(@json) calculations?
