Patch verb xapi/v1/Users({Id}) not working for CurrentProfileName

[AbrieViljoen]

Hi,

Using the https://mycompanyname.3cx.us/xapi/v1/Users({Id}) enpoint I can "Get" the "CurrentProfileName" for my user, but when I want to try and change the "CurrentProfileName" with a "Patch" command it just does nothing. I tried to change the "FirstName" with a "Patch" command and that works fine, so it seems like my coding is correct and something else is preventing the "CurrentProfileName" value specifically from changing. Can anybody please help with a solution or maybe know if this is a bug in the current version of 3CX?

 

[Evolute IT]

That's because it's only a reference property. There's no way to change the status currently in v20. The API will probably be there once they add back the feature to change a user's status from the admin, like in v18. V20 is still early in the release cycle and will get many updates most likely.

 

[AbrieViljoen]

That's because it's only a reference property. There's no way to change the status currently in v20. The API will probably be there once they add back the feature to change a user's status from the admin, like in v18. V20 is still early in the release cycle and will get many updates most likely.

Thanks for the info. I suspected that it might just be a reference property. I'll keep checking then after every update if they've activated the update of the "CurrentProfileName" through the xapi.

 

[VoIPTools]

It is possible to do using the 3CX Call Control API rather than xapi

 

[AbrieViljoen]

It is possible to do using the 3CX Call Control API rather than xapi

Thanks for the tip, but it's not that easy. I work in Delphi RAD Studio, so the xapi allows me to make a single simple api call to me 3CX instance and get the status of an extension, super easy. If I use the 3CX Call Control API I will first have to create a wrapper as a middle-man between .Net and Delphi, then run that wrapper in a Delphi app on the server that provides me access to my own api to change the status of the calls. It's too much work for something that should be simple to do.

I'll wait it out and see if the xapi will allow me to change the status in later releases, otherwise when I have some time to waste I'll do the wrapper and my own api to get it done. For now at least I can show the status of each extension to my team in our admin app and I've setup our YeaLink phones with shortcuts to quickly change the status of a user, it get's the job done.

 

[Evolute IT]

Oh Gosh Delphi