What I’d like to be able to do:
Copy a form and have a complete copy of it available to modify, including copies of any item templates used by the original form.
What’s currently available:
Copying the form copies the form itself, but leaves repeating panels pointing to the old item templates.
Feature request:
We should be able to choose which of these two behaviours we want when copying a form that uses templates.
4 Likes
Apparently this hasn’t been implemented, and it bit me today. I had an app that worked, but I wanted to try an alternate implementation, so I created a copy of a form that contained a data grid to experiment with the copy. I got the new method working and decided to then delete the original form. To my surprise, this deleted the row template associated with the data grid on the new form, forcing me to recreate the data grid… a non-trivial task.
I would suggest that the deletion of a form that contains a row template shared with another form should either (a) not delete the row template; or (b) warn the user. Implementing this suggestion, so that a copy creates a new row template automatically, would solve this problem.
2 Likes