I want to add a question:

If you already push a file to the device containing the data, why not already in the relevant (ini or xml) format?

From my side i maybe could help here only regarding ini file as we use this for a similar purpose but we generate it on enrollment on device side already.

Hello!

Our goal is to be able to do quick and clean reporting, while also ensuring devices are automatically renamed based on their current location whenever IP relocation moves them. (This can happen when new devices are added or when associates bring devices from one store to another.) 

We initially used Custom Attributes as a starting point. However, due to lag, devices were sometimes renamed using outdated attribute values instead of the current values inherited through the group. This delay is likely due to syncing between the device and the console. To address this, we want the process to complete in one seamless execution. ( We are on 2024.1.2.1046 )

We’ve been comparing Custom Data and Custom Attributes to determine which better suits our use case, and we’re leaning toward Custom Data since it appears to be more reliable.

I got our scripts functioning as intended and have them in a Signal Policy to trigger automatically upon group movement. Testing so far shows the reporting works exactly as expected. Here’s a summary of what happens on the script side in the signal policy:

• Retrieve the locationData.txt file via httpget and save it to the SD card.
• Verify the file exists, split the contents, and store the store number in a variable.
• Check if the required XML file exists; if not, create a new one with the proper structure and values.
• Once the XML is created, use the same value to send a device rename command and rename the device accordingly.

The steps above are executed using one Legacy script and one JavaScript script. 

To address some previous questions:

• The device groups do include a version of the store number, but for reporting purposes, we want something cleaner and more consistent. 
  • Example: \Company\Devices\EST\Stores\DEVICE_TYPE\DEVICE_TYPE_D00\000 vs. S000 
• When we call the httpget, the data comes in a raw format and must be parsed to extract the needed values. 
  • Example of returned data (regardless of file format):
    • DIVISION=000
    • STORE=00000
    • STORENAME=S000 

I also never thought about using API calls within the lockdown and that could be very beneficial.

I never used/tried it but in JS you should be able to do http get like this (ofc a lot to build around the result and so on still needed):

function httpGetAsync(theUrl, callback)
{
    var xmlHttp = new XMLHttpRequest();
    xmlHttp.onreadystatechange = function() { 
        if (xmlHttp.readyState == 4 && xmlHttp.status == 200)
            callback(xmlHttp.responseText);
    }
    xmlHttp.open("GET", theUrl, true); // true for asynchronous 
    xmlHttp.send(null);
}

Source: https://stackoverflow.com/questions/247483/http-get-request-in-javascript

And then no need for a kiosk, just use a task profile after you verified your script, you send to the test device manually works fine.

Take the result of the http get then and continue working on it before saving it as a file to the sdcard folder.