Primo VE: Record elements tag field in file splitter of generic XML discovery import profiles to support X-Path
In discovery import profiles for Primo VE, generic XML profiles do not currently support X-Path within the Record elements tag of the file splitter.
This means that XML source files which contain a multi-layered structure within records are not accepted by Primo VE on import. The file then has to be manually transformed to remove the extra layer before importing.
For example, a XML file generated from one of our external systems pulls in data for some fields from additional tables to the bulk of the record, adding an extra layer to the record e.g.
root element: <table>
record element: <tuple>
path to most elements in record: tuple/atom
some field have extra layer in following format: tuple/table/tuple/atom
It would be beneficial if the record elements tag could support X-Path, in a similar way to the identifier tag and location of deleted status fields within the file splitter.
Amanda Swann
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 30 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Primo.
Best regards,
Primo Product Team