How to use config excel file from orchestrator assets.?

[Sanket_Shinde1 (Sanket Shinde)]

Hi Team,
Good evening!!

I want to use config file from orchestrator asset in the from of json.

please let me know steps to follow. like excel config file to convert to json
then upload on orchestrator asset

access in workflow

[Anil_G (Anil Gorthi)]

@Sanket_Shinde1

Just save the json string in an asset and then retreive the asset using get asset and then deserialize the json to access it

Cheers

[Gokul_Jayakumar (Gokul Jai)]

Hello @Sanket_Shinde1
Kindly refer to this thread,

Upload json config file to Orchestrator

Hi @jenkim, You can copy your json content as-is to a Text Asset and save it in the Orchestrator. Use Get Asset activity in the Studio/Robot Use Deserialize Json activity and access your specified keys in your Json string (config) (You can find this activity in UiPath.Web.Activities package from the offical feed). This is extremely fast and has worked really well for us. Is fast, scalable and not the least, reliable. Advantages: Your text asset can be easily manipulated before running you…

[mkankatala (Mahesh Kankatala)]

Hi @Sanket_Shinde1

→ You can copy your json content as-is to a Text Asset and save it in the Orchestrator.
→ Use Get Asset activity in the Studio/Robot
→ Use Deserialize Json activity and access your specified keys in your Json string (config) (You can find this activity in UiPath.Web.Activities package from the offical feed).
This is extremely fast and has worked really well for us. Is fast, scalable and not the least, reliable.

Advantages:

→ Your text asset can be easily manipulated before running your process either manually or programatically. For example, you want to add more config parameters to your json, just go to orchestrator and edit the asset or edit the asset via the robot at runtime.

→ Your json string can be pasted as-is with double quotes, which is a must for json string. Orchestrator takes care of encoding characters.

→ Using json config can store many config values within it and makes it easy to move from dev to prod environments.

→ You only call the Get-Asset once per runtime to get all the parameters the robot needs

Disadvantage:

→ Deserialize is a must in studio or robot to get the values. Can be little work to set it up, but once you do, you can forget it!

[ppr (Peter Preuss)]

@mkankatala

→ You can copy your json content as-is to a Text Asset and save it in the Orchestrator.
→ Use Get Asset activity in the Studio/Robot
→ Use Deserialize Json activity and access your specified keys in your Json string (config) (You can find this activity in UiPath.Web.Activities package from the offical feed).
This is extremely fast and has worked really well for us. Is fast, scalable and not the least, reliable.

Advantages:

→ Your text asset can be easily manipulated before running your process either manually or programatically. For example, you want to add more config parameters to your json, just go to orchestrator and edit the asset or edit the asset via the robot at runtime.

→ Your json string can be pasted as-is with double quotes, which is a must for json string. Orchestrator takes care of encoding characters.

→ Using json config can store many config values within it and makes it easy to move from dev to prod environments.

→ You only call the Get-Asset once per runtime to get all the parameters the robot needs

Disadvantage:

→ Deserialize is a must in studio or robot to get the values. Can be little work to set it up, but once you do, you can forget it!

content is taken from: Upload json config file to Orchestrator - #8 by jeevith

[Sanket_Shinde1 (Sanket Shinde)]

Thank you so much Guys

Cheers!!!

[ppr (Peter Preuss)]

@Sanket_Shinde1
May we ask you to mark @Gokul_Jayakumar’s post as a solution since he was the first to reference the post that helped you. I have only made the original source transparent to the copy-paste post above my post. Thank you very much for the support.