|
|
Untitled Document
|
Exact Synergy Enterprise
When trying to fill a custom field for requests, i get the error 'Non existing property' on the custom field
This error is given when you try to fill a request through the Repository or webservice, and the custom field you are trying to fill isn't part of the request definition for that request. This is due to the request validator assuming that any custom field will only be supplied if it is known that that field is part of the request To avoid this error, either make sure not to provide this field unless you know the request requires it, or add this custom field to all request definitions that your solution is likely to make. For this reason, it is also advisable to only use one of the generic endpoints (Exact.Entity, Exact.Entities and Exact.Entity.REST) when accessing the webservice in an administration that contains custom or Configurator solutions, because the entity specific endpoints will always try to pass all fields in the metadata, even if they are not used.
|
 |
|
Document Number: 26.421.383
Disclaimer
|
|
|