Dump Sources, cloud

Yep. Its pretty much Cloud ready, they just need to fix their Paths and viola.

Of course add more Dump Sources checkboxes to like Electronic Interfaces, EDI what not which we can enable in config. I know BPMs and EFX for sure have it. Maybe even EI.

Posting Rules sources are good too to se when developing Custom Rules.

Dumping it to the file share would mix live and pilot though
I doubt they will make dual configs for us.

Sounds good. unless externalsStorage has something to do with dump dir.

@hkeric.wci to clarify, you get \Server\BPM\Sources\#Efx even though #Efx is not explicitly called out in types section, correct?

Also that disabled=“false” is used to turn BPMs for debugging off system wide. They should make that Cloud friendly. Sometimes easier to disable all BPMs to test if its your or Epicor

<customizationSettings disabled="false" intermediateFolder="/epi/fs" loadPdb="false">

Yes it builds sub-folder Sources and inside I get:

When I used TEMP it wrote it to the Service Accounts Temp folder but again it made a sub-folder Sources.

Once you change the path you must either restart the pool or recycle I can never remember its one of those. Then you must trigger a BPM change like Disable/Enable to see it write.

isnt there already dual configs? - separate containers and connection strings, etc

Maybe so.

I updated my case, and asked for it to be pointed to my epicordata directory.

We will see what they say, and if needed I will reach out to my contacts on the cloud team directly.

Would probably be best to have it put in the admin folder of EpicorData. Therefor it would be available in server file download under Admin like the server logs and base EI files.

I thought about something like click the menu and get them locally

Well, here is something adjacent, the ability to set traceflags in outbound and receive back callertrace and detailed application server log output.

You can at least see some stack trace and sql info that way upon executing.

https://www.epiusers.help/t/dev-tools-developers-swiss-army-knife-server-logging-file-download-efxeditor-appstudiojsoneditor-baqaliaseditor-reporteditor-ssrsdesignpreview-bpm-linq-on-the-fly-dataview-component-cookie-localstorage-editor-xmlhttprequest-parser-kinetic-dashboard/127887/204?u=gabefranco

An interesting thing is that every time you compile a function (demote/promote cycle) - a revisioned compiled copy is saved, i don’t see it exposed to the user anywhere, but you can see it in the backend.

I’ll look to see if there’s a knob exposed.

Any luck? They’re telling me Host.config cannot be changed.

Did anyone manage to make headway on this? I think this may be a wall I just ran into as well.

It’s working in the cloud but the files are being dumped in a directory thats ‘not normally’ accessible.

If you’re at Insights, ask the experts.

Yeah, something to keep in mind for potential attempts and solutions is each API request can go to a different container/IIS instance. Meaning that any file storage/access location would have to be shared between containers for reliable access. Consistency between containers now sems a lot better but earlier on, let’s just say having different behaviour depending on which container was used to serve each request was the stuff of nighwares for troubleshooting.

Interesting. Not sure I follow. Are you saying, for example, that in File Server Download or via sandbox.io the file list in incomplete or they’re potentially listing files from multiple servers??

Yes, anything company/instance specific/saved would be saved outside the container. Containers for the most part should be considered generic and disposable at anytime. Therefore, unless ‘temporary’ files are configured to be saved and loaded outside the container, such temporary and inconsistent access challenges are likely to occur.

insert safe harbor, but an answer is coming.

Are these the files that you are looking for?

lol @klincecum laughing.

I never bothered playing around with the dump sources thing so idk what files are expected from that but I dug around on the cloud server we have and found these.