Profile Configurations goes blank when a new Profile Version gets created after doing a PUT on MobiControl/api/profiles/{referenceId}/packages

Profile Configurations goes blank when a new Profile Version gets created after doing a PUT on MobiControl/api/profiles/{referenceId}/packages

We are currently trying to automate the release process using the MobiControl API and we've encountered an issue where the Configurations in a Profile get lost when a new Profile Version is created via MobiControl/api/profiles/{referenceId}/packages

Our automation process is roughly like this:

  1. Get a token.
    Send POST to MobiControl/api/token
    This works.
  2. Upload a new version of our app
    Send POST to MobiControl/api/packages
    This works.
  3. Retrieve the Packages list for the Profile we want to update
    Send GET to MobiControl/api/profiles/{$profileReferenceId}/packages
    This works.
  4. Update the Profile, using the list from the step before and updating our app version number to the latest but leaving other packages as is
    Send PUT to MobiControl/api/profiles/{$profileReferenceId}/packages
    This works BUT we cannot set the Profile Configurations and they do not seem to get copied like when we do this manually in MobiControl WebConsole by doing Edit on a Profile.
  5. Assign the Profile to a Device Group to push out the latest version of the app
    Send PUT to MobiControl/api/profiles/{$profileReferenceId}/assignment

So this leaves us with some questions:

- Is this a bug where the Profile Configurations don't get copied over to a new Version when using the API?

- Is there any way to set the Profile Configurations using the API?

 

Here is a screenshot of how the Profile looks before running the automation process:

Here is a screenshot of how the Profile looks after running the automation process:

 

  • 30 April 2021
  • SOTI MobiControl
  • 4 Answers
  • 0 Upvote
  • 2 Followers
  • 537 Views
    • 4 Answers
    • 0 Upvote
    • 2 Followers

4 Answers

Order By:   Standard | Newest | Votes
JCMOD@SOTI | posted this 07 May 2021

Hi Krumutu,

 

Thank you for posting in SOTI Central.

 

This looks like a bug to me. Please proceed to raise a Support Case through support@soti.net / support.eu@soti.net. We can then look at resolving this moving forward.

 

On top of the above, I'll perform a test early next week and update you here to confirm if it is present in 15.3.1 or not.

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
JCMOD@SOTI | posted this 12 May 2021

Hi Krumutu,

 

I managed to test this just now, the issue persists on 15.3.1. As a result, I suggest you raise a Support Case via support@soti.net / support.eu@soti.net. In the meantime, I also suggest you split the package into its own profile so that you can utilize our API to achieve your desired behavior.

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Krumutu | posted this 12 May 2021

Thank you for the help and with testing and verifying.

Can you give me a better explanation of what you mean by splitting the package into it's own profile, I'm not sure I fully understand as I am new to working with Soti.

  • 0
  • 0
JCMOD@SOTI | posted this 13 May 2021

Hi Krumutu,

 

Rather than using the profile that has an existing Profile Configuration, look into using a new profile that only uses Packages rather than both.

 

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback