pverley
February 11, 2025, 4:42pm
1
Hi @pverley ,
You are not missing anything– currently the isPrimary field is not clone-able and is not supported by carry forward. I’ve added an issue to our GitHub to track this request so we can change this in the future:
opened 06:52PM - 12 Feb 25 UTC
1 - Bug
**Describe the bug**
> (Running `specifyconsortium/specify7-service:v7.9` on se… lf hosted server)
>
> My colleagues from NOU herbarium noticed that `Collector:isPrimary` field is never prefilled when **cloning** or **carrying-forward** a `CollectingEvent`.
>
> Configuration form of the carry-forward in the meta menu shows a **disabled checkbox** for `Collector:isPrimary` field.
>
> 
>
> [Bulk Carry Forward post](https://discourse.specifysoftware.org/t/bulk-carry-forward/1940/1#p-3745-configuration-2) reminds us that :
>
> > Carry Forward configuration, where each non-unique field and relationship features a checkbox that can be selected or deselected to customize what will be carried forward.
>
> But there is no `Uniqueness Rules` associated to `Collector:isPrimary` field in our Schema Configuration.
Related to https://github.com/specify/specify7/issues/2300
**To Reproduce**
Steps to reproduce the behavior:
1. Create a Collector record and check "Is Primary"
2. Try to clone or carry forward the Collecting Event record
3. See that you cannot configure "Is Primary" to be carried forward and that it is lost when cloned
**Expected Behavior**
This field should be supported by carry forward and should be clone-able.
**Reported By:** Philippe Verley at IRD on the [Speciforum](https://discourse.specifysoftware.org/t/collector-isprimary-field-cannot-be-cloned-or-carried-forward/2333?u=grant)
Thank you for reaching out!
Grant
February 12, 2025, 6:54pm
2
Hi @pverley ,
You are not missing anything as you cannot currently clone or use carry forward with the isPrimary field in the Collector table.
I’ve created an issue on GitHub to change this rule so that this field becomes available:
opened 06:52PM - 12 Feb 25 UTC
1 - Bug
**Describe the bug**
> (Running `specifyconsortium/specify7-service:v7.9` on se… lf hosted server)
>
> My colleagues from NOU herbarium noticed that `Collector:isPrimary` field is never prefilled when **cloning** or **carrying-forward** a `CollectingEvent`.
>
> Configuration form of the carry-forward in the meta menu shows a **disabled checkbox** for `Collector:isPrimary` field.
>
> 
>
> [Bulk Carry Forward post](https://discourse.specifysoftware.org/t/bulk-carry-forward/1940/1#p-3745-configuration-2) reminds us that :
>
> > Carry Forward configuration, where each non-unique field and relationship features a checkbox that can be selected or deselected to customize what will be carried forward.
>
> But there is no `Uniqueness Rules` associated to `Collector:isPrimary` field in our Schema Configuration.
Related to https://github.com/specify/specify7/issues/2300
**To Reproduce**
Steps to reproduce the behavior:
1. Create a Collector record and check "Is Primary"
2. Try to clone or carry forward the Collecting Event record
3. See that you cannot configure "Is Primary" to be carried forward and that it is lost when cloned
**Expected Behavior**
This field should be supported by carry forward and should be clone-able.
**Reported By:** Philippe Verley at IRD on the [Speciforum](https://discourse.specifysoftware.org/t/collector-isprimary-field-cannot-be-cloned-or-carried-forward/2333?u=grant)
Thank you for your post!
1 Like
system
February 19, 2025, 6:55pm
3
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.