Hey
I noticed today that services that have previously worked is no longer working in our dev environment, and i’m not sure why (no changes has been made to the services or the actions calling them). Still working in test and prod environments, have not pushed the new appfarm version to these environments yet. Tried to roll back dev to a nearly identical version as the one in the test environment, but still wont work.
To give an example:
We use a service that updates booleans on a stakeholder object. A action is called, and then we use a action param to determine which boolean property should be updated with invert boolean through the service. Even though the service is called every time the action runs, it only successfully makes changes on one of the 11 different booleans. No error messages or warnings in the devlog. And again, no changes have been made to the service or the action.
Any known service related problems with the new appfarm version, or any ideas?
Hi,
To check if it is related to the version (we have no known issues), can you deployt to Test (i.e. same model and version in both) and check if it works? If so, I would guess you might have som load-issues in Dev.
Also, have you checked the execution log and/or service validation of the Service (in the Devtools for Services)?
Hi,
Tried pushing to test, and that made the service stop working. Rolled back, then it works again.
Checked the devtools for services as well now in dev, no errors and the service runs “successfully”
Still worked in test on that same boolean (after push), so identical results to what i’m currently experiencing in dev.
Ok,
Might sound like some issue.
Can you send enought info (screenshots etc) of that setup in DM, enough for us to set up a similar case to reproduce? Or make a copy of that service and grant access for us (to copy setup).
FYI, a regression error har been found in the platform related to this.
It happens when multiple query params are mapped to the same runtime datasource (not service variables, but a single-cardinality data source) in a Service Endpoint. Previously, the object was created “with the first parameter” and updated with the others. Now, all of these replaces each other, meaning only the last query param will update the object.
Workaround: Tick “Autocreate” on the data source (or map to Service Variables). Probably not too many affected, but the fix will be patched once fixed.
