I have some calculations that have bizarrely simply stopped working in developer. This affects a single table only - other calculations are all running as normal. I tried setting up a new simple calculation on the problem table that returns a text value based on another field value and it simply does nothing when the field value is changed. It all still works as normal in the deployed solution - only in developer it doesn’t which is disconcerting to say the least!
Anyone else ever seen this?
How do I fix it?
UPDATE: Hmm - just uploaded new version to demo server and the calcs no longer fire there either! So all calculations on one table are not working but are fine everywhere else. Help?!
So in the demo server with the previous version it worked and with the updated not.
Then if you check what has changed between these in your version control system, then something must pop up.
Try reverting to a working solution and then go forward until the problem reoccurs.
No errors I could see in the log, but I have backtracked the changes and it looks like the issue is linked to the use of a virtual foundset based on the table in question during the login process but prior to the user actually being logged in. I’m not sure of the mechanism at play here but taking those steps out does fix the issue and the calculations work again.
I had assumed the issue was to do with the calculations themselves but your pointer to look at all changes prompted a wider search for the cuplrit, so thanks!