When I query the employee a certain charge is linked to, it returns the employee's username instead of the account record id.
I've noticed in several instances that the CommitCRM low-level API does this. It returns human readable values that it will not accept in return. In the past, I've been able to work around the issue by substituting the output returned by CommitCRM with the equivalent input, as specified in the documentation.
This issue, however, cannot be worked around in the same way.
I would get around this inconvenient behavior in my application by simply querying record ids using the employee username (FLDWRKUSERNAME) as a search field, but as I was informed in this thread, user details cannot be queried from the low level API because of some sort of security concern.
How is somebody using CommitCRM's low level API supposed to get the employee account record id from a linked charge record id?
I've noticed in several instances that the CommitCRM low-level API does this. It returns human readable values that it will not accept in return. In the past, I've been able to work around the issue by substituting the output returned by CommitCRM with the equivalent input, as specified in the documentation.
This issue, however, cannot be worked around in the same way.
I would get around this inconvenient behavior in my application by simply querying record ids using the employee username (FLDWRKUSERNAME) as a search field, but as I was informed in this thread, user details cannot be queried from the low level API because of some sort of security concern.
How is somebody using CommitCRM's low level API supposed to get the employee account record id from a linked charge record id?
Comment