simPRO API Forum

Hi team

Using custom field filters with API endpoints remains broken since the update to 25.1.1 on Jan 12th: viewtopic.php?f=3&t=2815

There are currently four forum threads either raising or hinting at the underlying issue:
viewtopic.php?f=2&t=2812
viewtopic.php?f=2&t=2809
viewtopic.php?f=2&t=2656
viewtopic.php?f=2&t=2708

It's now Feb 13th, one month after the release of the API update that broke the custom filter functionality, and there has been no official acknowledgement of the issue or plan announced to fix it in a future update and when that might be

This affects core services that depend on custom fields to efficiently filter on specific jobs/entities. We've raised tickets on behalf of our clients and our clients themselves have called the help desk repeatedly. We have heard nothing back on a support case we raised over a week ago

I understand unexpected bugs can catch development teams off guard, we are no strangers to this experience in our line of work, however rarely would a whole month go by where there is basically no communication regarding the issue to affected clients

In the past we have had reasonably quick communication on the forums and acknowledgement of the issue. This exact same issue has come up in the past and it was addressed relatively quickly (acknowledged within a day): viewtopic.php?f=2&t=2654&p=7153#p7153

I'm not sure why this same bug has been treated differently this time around but we have been disappointed by the lack of communication and frankly below the standard of what I feel is reasonable in our industry
 
We are grateful to have a forum to discuss issues and engage in a dialogue with the simPRO team but please look into improving communication on reported issues, or at least give us some guidance on how we might better present issues to the team if you believe we are not going about it the right way

Andy Rees

Hi,
Defects are usually reported to our Simpro helpdesk so they can verify the issues and register the clients details so we have the information needed when we are working on solving an issue and need to recreate for debugging.

I can confirm that we have had reports of the custom field filtering being broken and we have had tickets created based on this that are being picked up for development. I can not give a specific time for when this will be solved but we are working on it.

We will update here when a fix has been released. And if you experience this and have not reported it please do so as we can then have an overview of the scope of the issues and test more use cases to ensure it's fixed. This also gives you a ticket number for communication.

Regards

OK useful to know that is the preferred method

We did log a ticket for this issue on Feb 3rd, Case Number: 968668, but never got a response beyond the automated confirmation email