As Script Config blocks get modified due to instance numbers changing or
perhaps deleted because it's no longer needed... there's inevitably going to
be a buildup of unneeded ScriptSource TXT and ScriptCompilation XML files
in their respective folders.
Any plans for a routine or command that will clean out the obsolete files by
comparing database instance numbers to the file's instance numbers in the
This has not been talked about yet. Right now the only way to clean them up is to manually delete the files, which is not user friendly and is highly prone to errors.
I agree that an automated process would be much safer. @Jim_Okapal can you create a "feature" tagged post as a request for such a command?
First time I'm adding a tag. If I add the tag word "feature" to the main post,
does it qualify or do I need to start a new post? It's now added to this one at
On any post you can click on the "feature" label and it will be added and help group things in the discussion.
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!