Debug logging in the cloud

[Brian (Brian Versfeld)]

For some of the BPMs and Epicor Functions that I write I build in some logging to a text file. I found a way to do this in the Epicor cloud additional/pilot environments by writing to F:\epicordata[Site ID][Site ID]\Users[Epicor User]\log.txt. I am then able to download the file through the Server File Download program in Epicor. This works fine both by calling the Epicor Function in Epicor or calling the Epicor Function via REST.

However, for the production environments it works different. The drive where the epicordata is located should be the G drive. So i write to G:\epicordata[Site ID][Site ID]\Users[Epicor User]\log.txt. When i call this function from within Epicor this works fine. But when i call this function via REST it throws an exception that says it cannot find the file/drive. I checked which part of the directory could not be found and it seems to be the entire G:/ drive. I assume the cloud team configured the security rights of the production environments drives different than for additional/pilot.

Currently i do face an issue and it would make my life a lot easier if i was able to log to the specified folder on the production environment. Is there any way to make this possible? Or is there a better way to implement debugging in the cloud environment?

Thanks in advance!
Brian

[Mark_Wonsil]

See this thread on how to get the EpicorData location.

10.2.600 & AR Invoice Form

Like Paul says, anything in the EpicorData folder is accessible from the Server File Download. Windows Event Logs are not, which IS a problem for SaaS users. If you’re going to write to server’s file system, ALWAYS use the EpicorData folder. You can use this code in a BPM to find the path - which we never hardcode because you never know where it might be during a rebuild, moved to the cloud or whatever… // ServerPath //public struct PathInfo //{ // public bool IsFile; // public string Full…

[Brian (Brian Versfeld)]

As i mentioned, i do know the location.
The problem is that it can’t be accessed when invoking the Epicor Function via REST.

[Mark_Wonsil]

Correct. Providing file access to the server is a ginormous security risk. Use FileTransferSvc instead.

Download to our Server from Cloud

Yes, the Ice.LIB.FileTransferSvc in REST can do that for you. [image]

[Mark_Wonsil]

As for better debugging, cloud or otherwise, you may want to add a vote or more to the DevOps idea for improved logging support.

https://epicor-manufacturing.ideas.aha.io/ideas/ERP-I-139

[tkoch (Theodore Koch)]

Try this approach

How to write to task log from scheduled Functions

This should get the job done, could convert this to its own function and call it whenever is needed from another function. Should be useful as well to write out logging in cloud when debugging functions (or bpms) with no event viewer access Action<string> writeToTaskLog = (message) => { foreach (var activeTask in Db.SysTask.Where(t => t.Company == Session.CompanyID && t.TaskDescription.ToLower() == "run epicor function" && t.TaskStatus.ToLower() == "active")) { var taskLog = Db.SysTaskL…