API Person Provider - mobile number behaviour

lock
push_pin
done
Besvarat
0

Hi,

When using the Person archive provider, we have noticed behaviour that has caused us some problems when syncing with a 3rd party.

Take this example where we have a Contact with only the Phone number entered:

 

When calling the API, we see the results as expected:

 

However, if we populate only the mobile number:

 

The API returns the number for both the Phone and Mobile:

 

We have managed to code a fix, by checking if the TooltipHint value points to the same phone_id, but we were unsure if this behaviour is intended or not?

When both the Mobile and Phone are entered, the API result is as expected:

 

For reference here is the Body of the call to FindFromRestrictionsColumns (agent):

Cheers

Rich

 

 

16. juli 2025 | 02:33 em

Allt Svar (0)

Lägg till svar