Filtered Job API Issue
Posted: Wed Jan 29, 2025 2:42 am
Hi Simpro team,
Could I please have a Simpro tech look into the below as this API and similar ones were working previously and now arn't.
I'm having an issue with jobs API routes using specific filters for custom fields, technicians and stage.
The Sandbox version of this API route works perfectly, however not in our company build which is causing me to think there is an issue with our build.
Routes below are tested using Postman.
Sandbox API route:
enterprise-sandbox-au.simprosuite.com/api/v1.0/companies/{CompanyID}/jobs/?columns=Customer&CustomFields.CustomField.ID={ID}&CustomFields.Value=Yes&Technicians.ID={ID}&Stage=in(Pending,Complete,Progress)
Company API route:
{companySubDomain}.simprosuite.com/api/v1.0/companies/{CompanyID}/jobs/?columns=Customer&CustomFields.CustomField.ID={ID}&CustomFields.Value=Yes&Technicians.ID={ID}&Stage=in(Pending,Complete,Progress)
If I remove the custom field part of the filter from the route it works, however the custom field ID and custom field value are 100% correct after checking mutliple times, also again this was an API that once worked.
Thank you for the help,
Kind Regards,
Jourdan
Could I please have a Simpro tech look into the below as this API and similar ones were working previously and now arn't.
I'm having an issue with jobs API routes using specific filters for custom fields, technicians and stage.
The Sandbox version of this API route works perfectly, however not in our company build which is causing me to think there is an issue with our build.
Routes below are tested using Postman.
Sandbox API route:
enterprise-sandbox-au.simprosuite.com/api/v1.0/companies/{CompanyID}/jobs/?columns=Customer&CustomFields.CustomField.ID={ID}&CustomFields.Value=Yes&Technicians.ID={ID}&Stage=in(Pending,Complete,Progress)
Company API route:
{companySubDomain}.simprosuite.com/api/v1.0/companies/{CompanyID}/jobs/?columns=Customer&CustomFields.CustomField.ID={ID}&CustomFields.Value=Yes&Technicians.ID={ID}&Stage=in(Pending,Complete,Progress)
If I remove the custom field part of the filter from the route it works, however the custom field ID and custom field value are 100% correct after checking mutliple times, also again this was an API that once worked.
Thank you for the help,
Kind Regards,
Jourdan