Greetings, I created a simple robot that read a username and password from an Excel file, copied it into memory, opened a web page, loaded the users, and logged in. I developed it on my PC, and it worked perfectly. The Excel file was in the development directory.
Then, I uploaded it to the Orchestrator and published it in a folder to be used on another machine with the assistant. It turns out that it works correctly, but I don’t know where the Excel file is stored. When I developed it, I thought I would have to place it in the same path, but in reality, I didn’t install anything; I simply ran it with the assistant… it’s as if it comes with the package. Could it be that way? How should I ensure that it doesn’t remain embedded, as the idea is to update that Excel file from time to time?
If you put some file (such as xlsx) under the project folder, it will be included in the nupkg file.
And it will be extracted under %USERPROFILE%\.nuget\packages\[package name]
So, first, can you check the above folder? The excel file exists there.
If you need not to include the excel file in the package, please put the file in other place and use absolute path in UseExcelFile activity etc. (If you want to put it under Documnts etc, environment variable will also help you)
Yes, but my question is whether I can edit the files that are inside the NuGet package. When I searched for the Excel file, I noticed that the files we generally use for development in Studio are also there. However, they are inside a “Content” folder. I am unsure if it would be possible to open them with Studio without causing any issues.
In Windows project (or crossplatform project) xaml files are complied to dll file and executor run the dll files. So, we cannot edit program inside nupkg file. Source files may exist under content folder, however, they are no effect on execution.
Editing in the xaml files present inside .nuget folder would not reflect in your actual package or the package on orchestrator as it would be a local change
For any changes make the changes in actual project and yhen publish to orchestrator
Now coming to file…if we want it to be modified always then we need to place the file in any common folder like C:\botfolder\file.xlsx so that we can use same location in all machines and it can be exited
If plced in project folder then it would be packed along with project and will reside in the package folders
Alternately can store files in any shared drive or orchestrtor storage buckets etc and use it when needed …
Apologies for not concluding the matter. It turns out that there is an issue with the destination PC that does not occur on my PC. Therefore, my question arises from this issue. I see two possible solutions:
A) If I run the XAML within the NuGet package using the studio, will I be able to observe the local execution step by step to identify the problem? → I understand this has already been addressed.
B) An alternative is to examine the logs generated by the system, but I could not find them within the files in the package. Do they remain on the remote machine?
Hello Anil, thank you for your response. The issue was that I wasn’t encountering any errors; the bot would simply stop. I had inserted some log messages to monitor the process step by step, but I couldn’t find them. Initially, I thought it was an issue with the data being incorrectly retrieved from the Excel file. However, after your response, I saw that the data was correct, and then I tried to check the logs, but I still couldn’t find them. Nevertheless, I reviewed the code on my local PC and discovered the problem. It was a logical design flaw in the bot.
ashokkarale
Yoichi
Anil_G
Jon_Smith
wy572076601
Joe_Matuch
Aditi_Indoriya
ruchirmahajan
Somanath1
tomasz.wierzbicki