Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik GA: Multivariate Time Series in Qlik Predict: Get Details
cancel
Showing results for 
Search instead for 
Did you mean: 
sshastry
Contributor II
Contributor II

GET LOADSCRIPT - Method Not Found During execution of the automation

hello 

I have created an automation using a service account user in a Shared Space. The automation reads the load script and finds a particular table if that exists in the script. this is helpful for us as we have a distributed Qlik develop environment and we would like to inform the owners if we are changing underlying models.

When I am logged in as that user (service account user), the automation works  and identifies all apps that users a particular table.

But when the same automation is run by another user who has access to the shared space,  an error message is generated esp when the API call is made for Get LoadScript.

what am I missing? 

Labels (1)
6 Replies
DaveChannon
Employee
Employee

We probably need some more details, but generally users must have the codeveloper (Can edit data in apps) role to access the load script. Does the user have that level of access?

sshastry
Contributor II
Contributor II
Author

Hello Dave,

Thank you for responding.   I reviewed the link you sent and "full disclosure" - I am a bit lost. Are you saying that I have to assign a role to the service account user via an API call? There is no way to do that through UI? I am not well-versed in using APIs, and automation is great because it has code blocks that works for our need.  

Please know that I have created this automation for myself in my personal space and then I copied that exact same automation to the DEV shared space for our team to use. I am a tenant admin and that exact automation works when "I" run it from my personal space.  but the issue is that when I am logged in as a service account user and run the automation from the DEV - shared space I get the error.

I have 3 attachments.  One shows the role the user has, 2nd shows the access the user has on a space against which I am running the automation and 3rd is the error I am getting when running the automation as service account user.  

What other information might be helpful to you.  Thank you for your time

sshastry
Contributor II
Contributor II
Author

Hello Dave, I added more notes to the question.  Can you review those if you have time? I surely do need help as I am trying to use automations and getting stuck while making it available for a larger user base.  Thank you 

DaveChannon
Employee
Employee

I just verified this works in my environment - both for apps in a shared and a managed space, where the executing user has access to the app, but isn't the owner, so there's something else at play. Method not found is not an error I'd expect to see.

I'd open a support case to dig deeper, if this isn't yet resolved.

vkramBI4Qlik
Contributor III
Contributor III

Agree with Dave on level of access as the issue. We did the same kind of work in creating the automation to identify the list of apps that uses a specific table in the script in the whole tenant. In our case we had to provide the tenant admin access in order for the automation to be read the script residing in the app. I tested it with couple of users and confirmed on this. Hope its the same with yours.

Thanks.

sshastry
Contributor II
Contributor II
Author

Thank you @vkramBI4Qlik for responding. 

Since you mentioned providing the tenant admin access to the service account user,  that is one thing I have not done.  The service account user is NOT a tenant admin.  Let me try that and see if that helps.  Thank you.  

I would like to dig this a bit further with the community, though, because everyone who will "write" an automaton or "use" it may not be a tenant admin.  I would want to get help in identifying what  roles/permissions this user should have -  who is the owner of the automation, for "others" who are regular users to run the automations.

Thank you again for keeping the thread alive.