SOTI Pulse Logo

Custom Data - Managed Google Apps

ÖC
Ömercan C.
Spital STS AG

Hi

I have a question about passing custom data to a Managed Google Play app. The data is stored in a JSON file and is accessed using custom data settings. This works perfectly within Soti (e.g., Lockdown, CustomMessage, etc.).

However, as soon as we try to pass these values to a Managed Google app, it doesn’t work. I’ve learned that Soti plans to support this in v2026.

Do you have any ideas for how we could implement a temporary workaround?

Here’s an example to give you a better idea:

Thank you!

Best regards

Ömercan

Custom Data
6 months ago
SOTI MobiControl
ANSWERS
RS
Rafael Schäfer
6 months ago

Hmm, never tried with custom data yet.
Ever thought of (if possible) using custom attribute instead?

We use it to provide device/location specific data to app config like %CustomAttr:Country% and it works fine.

Also keep in mind that if you create/provide the json file to be read by the agent and then data provided to the console during enrollment may take more time than the app to deploy.
So, maybe you need to provide the entire process time and check later again.

1. Json provided/created to/on the device (custom data in the console still empty)
2. Json read by the Mobicontrol agent to custom data locally (custom data in the console still empty)
3. custom data provided to the console (after next check-in)
4. custom data provided to the app
    *somewhere between the app could have been already being deployed without data (as it was still empty)

ÖC
Ömercan C.
6 months ago

Thank you very much for your feedback.

Of course, I tried what you mentioned, but only the macros specific to Soti MobiControl (%DEVICENAME%, %MODEL% etc) are passed to managed Google apps and unfortunately, custom data is not transmitted.

If I understood the suggestion with %CustomAttr:xxx% correctly, this value would need to be set manually. However, since we have several hundred devices and each device has a different value, wouldn't that mean that all the data would have to be entered manually when using the custom attribute option?

RS
Rafael Schäfer
6 months ago

Depends.

If this value is device specific, you need to set this value when device arrives at the console (manually or via API).

If this value is group specific, you can define it for a device group once (manually or via API) it gets created and gets inherited to all assigned devices.

We use this to both, we create groups via API setting also their group specific attributes with following API calls.
And we have device specific attributes, where an API cron-job is running, checking for new devices, filtering for something specific, only pointing to new devices and then setting the relevant attributes for these device(s).

Similar Discussions