Community
Showing results for 
Search instead for 
Do you mean 
Reply

Descrepancies between Metadata and Results

New Member
Posts: 4
Country: Australia

Descrepancies between Metadata and Results

It appears that the returned results do not match the described metadata for the standard fields

 

For example, compare the two datasets

 

/Act.Web.API/api/metadata/fields?recordType=Company

/Act.Web.API/api/Companies/{id}

 

Some examples of fields that don't match:

- fax

- numberOfEmployees (Example attached)

 

 

This occurs on both the Companies and Contacts

 

Version: 18.1.108.0

New Member
Posts: 4
Country: Australia

Re: Descrepancies between Metadata and Results

In addition

 

When setting custom fields, the field name must be entirely lowercase. Although the metadata doesnt reflect this

 

Regards

Employee
Posts: 38
Country: USA

Re: Descrepancies between Metadata and Results

Yes, currently the metadata does not represent the API response model fields, except for the fields defined in the picklist response.  We currently have a defect that will resolve this issue.  I will post an update to what version it will be released in as soon as I can.

Highlighted
Employee
Posts: 38
Country: USA

Re: Descrepancies between Metadata and Results

Thanks for the heads up on the lowercase issue, I will add this to the acceptance criteria in the defect.