You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The "Auto-Populate" button on type mappings will populate more than one option if there are multiple nested keys with the same name. This causes errors on processing where a node may pull the incorrect key when populating properties.
Workaround to deselect/reselect these things in the existing mapping: If you hit the little "x" button by the prop you want to get rid of, it clears all 5 (or however many) extra props, then you can manually re-select only the prop you actually care about.
Clicking "Auto-Populate" looks for anything called "name" and maps it to the name property. Since there are multiple things called name, it maps all of them. Then when the node goes to be created it grabs a random one of the names and chooses that as the name property. In this example it'd grab name, final_approver.name, and punch_item_manager.name and map them all to name. So it's populating the "name" property 3 times over, whereas if you select the field manually instead of auto-populating, it only populates with the field you want.
One way to tell if this is occurring is if the number of properties populated up top doesn't match the number of properties you want to populate. For example, if I was auto populating "name" and "id", I'd get 4 results from this example when I'm only shooting for 2 (id and name).
Impact
The bug fix will involve:
not picking multiple fields when autopopulate is clicked, and/or
very clearly displaying when multiple fields are selected for a single field.
There is currently no obvious way to tell this other than opening the drop down. The drop down is also kind of misleading because it shows all the fields being used in the whole mapping. Instead it should show only the fields that are selected for that particular property.
The text was updated successfully, but these errors were encountered:
Bug Description
The "Auto-Populate" button on type mappings will populate more than one option if there are multiple nested keys with the same name. This causes errors on processing where a node may pull the incorrect key when populating properties.
Workaround to deselect/reselect these things in the existing mapping: If you hit the little "x" button by the prop you want to get rid of, it clears all 5 (or however many) extra props, then you can manually re-select only the prop you actually care about.
Steps to Reproduce
In a dataset with this structure:
Clicking "Auto-Populate" looks for anything called "name" and maps it to the name property. Since there are multiple things called name, it maps all of them. Then when the node goes to be created it grabs a random one of the names and chooses that as the name property. In this example it'd grab name, final_approver.name, and punch_item_manager.name and map them all to name. So it's populating the "name" property 3 times over, whereas if you select the field manually instead of auto-populating, it only populates with the field you want.
One way to tell if this is occurring is if the number of properties populated up top doesn't match the number of properties you want to populate. For example, if I was auto populating "name" and "id", I'd get 4 results from this example when I'm only shooting for 2 (id and name).
Impact
The bug fix will involve:
There is currently no obvious way to tell this other than opening the drop down. The drop down is also kind of misleading because it shows all the fields being used in the whole mapping. Instead it should show only the fields that are selected for that particular property.
The text was updated successfully, but these errors were encountered: