I am having issues when publishing my StudioX Project. It runs fine when testing, but when publishing this error appears : ‘Config’ is not declared. It may be inaccessible due to its protection level.
So I had Config declared as a Global variable when I copied some of my code from Studio to StudioX.
You mentioned you copied stuff between projects. Did you also copy the global variables over? As far as I know they are stored in .project\globalVariables.json (a folder that’s hidden by default). Your safest bet might be to recreate the global variable in Studio’s data manager.
Thank you so much for the response, unfortunately it seems one cannot create a global variable in StudioX, do you maybe have another way of doing this?
If you still want to use StudioX then it might be helpful to know that all the variables defined with the “Save for later” activity are treated as global variables
Or you might want to try manually manipulating/copying the globalVariables.json. I’m assuming the original Studio project where you copied from did have this file, correct?
Out of curiosity, why don’t you use normal Studio? StudioX is meant for non-technical business users, and as such more technical concepts like global variables were intentionally hidden. As a consequence there will always be some friction and potential issues when trying to work with global variables in StudioX.
Thank you for the response! So, I resolved the issue, by removing all the workflows and just creating sequences within the one main file.
But thank you so much for the assistance!
SO why the project was initially created in Studio is because I normally do use studio to create my automations, but this one is an attended automation for a team, and they all only have citizen developers licenses thus, they can only run StudioX project, thus I had to recreate the project in StudioX.
Maybe I’m misunderstanding you… when you create an attended automation with Studio, why can citizen developers not run it via Assistant?
Also for future reference, note that it’s possible to open up StudioX projects with Studio. I haven’t tested how this would behave if you added global variables in Studio and then re-opened the project in StudioX. But it might be a potential way to do this for anyone else coming across this thread in the future.
Thank you for that information; I wasn’t aware of it. I’ll definitely keep it in mind!
I also recently learned that Citizen developers cannot run attended automations from Studio, even when using the Assistant. This came up during a call with a UiPath Agent, where we were troubleshooting issues with running the bot via Assistant. The agent informed us that the problem was due to license allocation.