Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Currently no, but that is possibly a good suggestion. Currently the solution is to use individual directories for individual importers. I'm surprised you report that to be the issue! I took a quick look at the code and it's checking if a listed file in the directory and shouldn't import in that case. I'll take a deeper look next week. You can have other files in the directory and have them be ignored, but only if they're named to begin with the imported prefix set on the data source, currently.

As you are likely the maintainer of the system, you should do what makes sense to you. Global scripts are simply stitched into scripts to provide functions or global variables or what have you. Refactoring what gets passed where and how in a script is an implementation decision that I don't see a clear advisement on. It certainly can simplify things if lots of scripts would be doing the same thing to make that a uniform function. The only thing I can think to add to that is that currently script engines which are in something's runtime do not suddenly execute a global scripts when it is saved to pick up the changes. You would have to restart any meta data sources or scripting sources, for instance.

Hi Nathan I do believe the OPC data source requires windows.

Good Morning Phil, You can cancel this request, I was able to solve my Authorization Request Header issue. Thanks again for all the help!!

Hi Craig, thanks for the swift reply and the detailed description! It actually did the trick -- many thanks! I would have never guessed from the documentation, that this would be the thing to do. But hey -- always good to learn something. Cheers, Frank

Perfect, thanks for your help @phildunlap . Much appreciated!

I'm largely a librarian of previously answered questions at this point :D

Hi Turbo, That's interesting, that's a 32 bit ARM device this time. Can you post the stack trace that was accompanying the 500 error so we can see if it's the same as the referenced thread?

@Turbo glad we got it all working for you!

@craigweb Hi Craig; Thank you for your assistance. that was exactly my issue. All are working fine now.

Success Terry, it was a capital I in an if statement within a script that was causing the invalidation.. Got it working between excel and open office I got it to preserve the " and all but I get what you are saying about not being strictly required and It probably works in Excel too Thank-you for all your guidance here. The new UI scares a bit me if I can jump back to the legacy screen. lol

@iperry said in Upgraded to 3.6 & Getting error when saving script: I like the white background when using applications as opposed to the black/grey of the newer layouts (not just Mango) but that is just my preference. Check out the UI settings under Administration, you can configure the color scheme to your liking. Great to hear there is nothing holding you back from using the new UI. Please do create a new thread if you find something that could be improved.

Hi ppaniceres, welcome to the forum! There's a simple example of writing to a file from a script within Mango in this thread: https://forum.infiniteautomation.com/topic/4208/creating-files-in-filestore-from-excel-post-process-script I would probably do this with a scripting data source on a cron like 0 * * * * ?

Hello Phil, Thank you for the update. In the mean time I will have to anonymise the spreadsheet templates. Cheers Brian

where would the event handler to create the Mango/RESTART file go? On the system startup event.

I would agree! I will make it behave the same.

Works like a charm.

Hi JMandina, welcome to the forum! If you post on the forum, you do not need to also send an email! To repeat my response email here: For some reason, the "Sync history prior to" setting on the publisher is set to six months. That is not the default (2 hours) and would result in the sync only attempting to synchronize data that was at least six months old. I would change that back to the default, 2 hours, and then rerun the sync. @Ralf has the right suggestion after that if it still does not sync, but I would expect them to after the "sync history prior to" setting has been corrected.

Thanks for sharing how you got it working!