Hello. I have recently been trying to use the clone function so I do not have to enter all of the information over and over again. However, sometimes the strat remarks are different. I cannot figure out how to change the strat remarks for one without changing them for all of the specimens. Has anyone else had this issue, any suggestions on how to troubleshoot?
Hi @Kyleeharford ,
Thanks for reaching out with your question!
The behavior you’re experiencing is because the Clone function is designed to create exact duplicates of the record, and as you’ve discovered, certain data fields can remain linked across the copies. It’s not ideal for the scenario you described where you need to customize each new one.
For what you’re trying to accomplish, I highly recommend using the Carry Forward feature instead. Carry forward allows you to configure the clone behavior on a per-field basis. It will carry forward all the data you want to repeat, but it will treat each new specimen as a separate entity. This means you can freely change the strat remarks on one record without it affecting any of the others.
Here is a link to the documentation that provides a step-by-step guide on how to use it: Form Meta Menu
Please let us know if you have any other questions after giving it a try!
Best,
Bhumika
Hi!
Thank you for the suggestion. I have been trying to use the carry forward function. However, I want to carry forward all of the collecting data except for the strat remarks within the paleo context. It will not let me do this. I have checked the box for it to carry forward to collecting data and to carry forward the paleo context (specifically excluding the strat remarks). Doing that resulted in all of the collecting data being carried forward, including the strat remarks. I then tried to carry forward all of the paleo context except for the strat remarks and did not carry forward the collecting data, but that resulted in nothing being carried forward, including none of the paleo context.
I am unsure of how to resolve this. It seems to carry everything or nothing forward, no matter what combination of things I ask it to carry/not carrry forward. Do you have any suggestions?
Thanks,
Kylee
Hello @Kyleeharford ,
Thank you for your reply!
We looked into your database configuration to understand what was happening. The problem is that your “Paleo Context” is currently set up as a shared record. The carry forward functionality is designed to bring over an entire shared record as a single unit, which is why you’re seeing it carry forward all the collecting data or nothing at all. It can’t selectively exclude fields from a shared record.
To get the behavior you’re looking for, we can change the “Paleo Context” from a shared record to an embedded one. This change would allow you to selectively carry forward specific fields within that context.
This is a relatively easy adjustment for us to make. It’s worth noting, however, that changing from a shared to an embedded record is much simpler than changing it back from embedded to shared in the future.
For a bit more background, here is a link to our documentation explaining the difference between the two record types: Shared vs. Embedded Records & Configuration
Please let us know if you’d like us to proceed with making this change for you.
Best,
Bhumika
Hi!
Thank you so much for the information. We are interested in changing the “Paleo Context” from a shared record to an embedded one so that we are able to change the “Paleo Context” for individual specimens. Please let me know when you plan to make this change so I can inform others on when we should not be using the database.
Also, when you make this change, could you take a look at the taxon tree? We are not able edit it without an error message being displayed. Tiffany Adrain has already emailed Teresa an image of the error message, so you are able to see what it is telling us.
Thank you for all of your help,
Kylee Harford
Hi @Kyleeharford,
So you can start moving right away, I resolved the case that was causing the crash in your taxon tree! There was a taxon node (‘Placeholder’) with an invalid rank that was created in 2015 that was completely invisible from the tree view and not linked to any records. I’ve removed this record so the error will no longer occur!
@SpecifyMembership can provide guidance on the timeline and work involved in that move, so we will be in touch soon!
Hi!
Thank you so much for looking into this for us. The taxon tree is working now on our end!
I will watch for an email for when they are going to change how our Paleo Context is configured.
Thanks again for all of your help!
Have a wonderful weekend,
Kylee Harford
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.