Hi all,
Incase other people aren’t aware, per the subject of this thread:
When you import a Generic Inquiry from XML, the XML contains a tag for
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<data-set>
<data>
<GIDesign>
<row DesignID="8b5104f6-326b-4194-a29e-b424601e5b61" Name="AR-Customers" FilterColCount="3" PageSize="0" PrimaryScreenIDNew="AR303000" NewRecordCreationEnabled="1" MassDeleteEnabled="0" AutoConfirmDelete="0" MassRecordsUpdateEnabled="0" MassActionsOnRecordsEnabled="0" ExposeViaOData="0" ExposeViaMobile="0" ShowDeletedRecords="0" ShowArchivedRecords="0">
</row>
</GIDesign>
</data>
</data-set>The DesignID here is what GI imports key from, so if you’re modifying a GI and don’t want to replace the original GI, you really need to update the DesignID to be a new value.
In the Modern UI issues thread:
There was a slight discursion between me &
I’ve been having issue with migrating GIs now. It used to be that the inquiry title and screen IDs were the only validation when migrating GIs to a separate tenant. Now, when migrating GIs, you can’t simply change the inquiry title and screen ID and then migrate the GI like we used to be able to do.
Inquiry validation seems to be based on NoteID now. So if the same NoteID exists for an inquiry in the tenant you are copying to, the GI import is going to erase that GI with the same NoteID.
In order to migrate a GI now, you have to Copy and paste the GI in the “From” tenant so that is generates a unique note ID, then you can migrate the GI over to the “To” and not erase the GI with the same NoteID.
My reply was:
As far as I know, that’s not new, at least if you’re dealing with XML Import/Export. DesignID (Which is I think the database field that you’re referring to as NoteID) has been the primary key for imports via XML for awhile. I keep getting caught out by this.
If you’re exporting/importing, another option is to just modify the DesignID GUID in the XML to force uniqueness.
I’m calling this out to it’s own new post, since it’s not strictly Modern UI.
I’m under the impression this isn’t part of Modern UI changes, and is just a different keying on an import process.
Questions/comments:
- I believe this is working correctly, but is non obvious. Do people agree?
- Better documentation/warnings on import would help, as users aren’t really offered clear information that they might be overwriting an existing GI.
- Has this behaviour changed? I don’t keep older versions on my machine to run regression testing.
- If it did change, when?
Edited to add:
But it would be really good for this to offer an ability to import as a new GI, rather than only offering a “will replace” option.