In the old form rules, I had the form rule attached below. I want to migrate the old form to a new form. However, QuickBase updated some of the form rules variables for instance one could have a field with a default variable like "has been changed" or "had been changed to" or "has been changed from". In the new form rules this is close to impossible. Anyone who has managed to fix this? I will appreciate.
Qrew LegendI agree that this is not a feature of new forms and it is a feature that would be nice to have. If you were so inclined, you could put in feedback and maybe other people will vote on that as well. But meanwhile "don't let the things you cannot do stop you from doing the things that you can".
I can see that you're just trying to update a field probably set to "Log Changes" for a down and dirty tracking of the previous statuses, including when and by who.
I suggest that you set up a simple Pipeline that will trigger on a change of that field and would update your logged field. So basically just have the pipeline do what the form rule would have done.
Yes and its being triggered by another field. I am not intending to use pipeline thats the last option when the problem knocks me down. Thanks Mark
If you don't want to go the pipeline route, you can set up a new field ex. Old Status. On your form rule, you can check if Status is not equal to Old Status. If that is the case, you can update the Log field and the Old Status. See screen shot (where Pet Type and OldPetType are comparable to your status.
The downside is it requires a new field and you would need to seed the new field for existing records.
This is an interesting idea. But the worry is how to get the form rule into the field. Let me see how I can twist it around.
