We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I click Clone on an existing Computed Field, I'd like for some of the fields to be carried over to the new form.
Don't want to have to repopulate all fields again when cloning a computed field.
Now if I click Clone. It brings up the new form, but it's blank.
I would say we should probably carry over the following:
I don't feel passionate about all the fields, but do what y'all think is best.
None
The text was updated successfully, but these errors were encountered:
I can implement whichever way y'all want to go with this. Let me know.
Sorry, something went wrong.
Thank you! Your proposed list of carry-over attributes looks good to me. Go for it!
Added changelog for #698
3d0c66a
FragmentedPacket
Successfully merging a pull request may close this issue.
Environment
Proposed Functionality
When I click Clone on an existing Computed Field, I'd like for some of the fields to be carried over to the new form.
Use Case
Don't want to have to repopulate all fields again when cloning a computed field.
![image](https://user-images.githubusercontent.com/29315002/125703224-301fd3ba-e2fc-47f9-bc48-8ac6cdd0cc56.png)
Now if I click Clone. It brings up the new form, but it's blank.
![image](https://user-images.githubusercontent.com/29315002/125703285-45b8e6ac-1204-4fa1-ad03-11a613e4e4d7.png)
I would say we should probably carry over the following:
I don't feel passionate about all the fields, but do what y'all think is best.
Database Changes
None
External Dependencies
None
The text was updated successfully, but these errors were encountered: