We would like the ability to export same entity relationships via the work area UI (e.g. item to item, product to product, etc.). Currently, the export capability can only export different entity relationships (e.g. item to product, item to resource, item to category, etc.). We would like to export item to item relationships to validate data is coming over correctly from ERP and/or manually completed as expected.
24 comments
November 08, 2019 09:34
We have the same issue, this would very helpful for us to validate our data.
4
August 10, 2020 11:35
Same issue with exporting Categories tree structure (ChannelNodes) which can have multiple levels created only by using ChanelNode-to-ChanelNode links.
4
July 28, 2021 20:42
We would like this as well
3
September 15, 2021 17:48
The lack of this ability is giving our team a bit of heartburn with Replaced By relationships.
3
September 16, 2021 16:59
Agreed. We have large amounts of Sections that are attached to other Sections in Plan & Release, with no way to export the relationships. Being able to export related entities that are the same as the parent entity would be extremely useful!
2
September 29, 2021 09:36
Another request of our team to be able to export "consumables", "additional" and "alternative" Item to Item relations to Excel....
3
December 07, 2021 12:55
I am also in need of this functionality in my customer project. Connect Item Accesories to an Item. Anyone above who has a workaround solution?
2
December 10, 2021 11:15
We would also like to export item to item relationships since we use "Related items" on the website and need to make a review of those links and compare with other language versions.
4
December 10, 2021 11:27
We also request the export function of relationships item to item, you can make relationships item to item but you can not export? Why not?
3
December 16, 2021 23:35
We use several Item to Item relationships in our data. The lack of this functionality makes it very difficult to audit and therefore maintain current relationships. As we all know, incorrect data can be quite frustrating both internally and to the end user. Please prioritize this.
6
January 11, 2022 18:42
We can't satisfy distributor request for accessory, cross-sell, upsell SKUs info. Please prioritize.
5
April 27, 2022 16:18
We too have the need to be able to export the "Related Items" - please prioritize.
5
May 03, 2022 16:27
That is interesting, I had another thought on a possible solution that also did not work. I a couple of different solutions to attempt a workaround for exporting all "Item works with Item" type of relationships. I set up two items with relationships to another item. So I have 2 "parents" each with a "child" item.
No matter how I query or search I only get the two parents returned. No way discovered to go backward on that link.
I even tried putting in a completeness rule for the existence of an item to item link. and it only shows complete on the parent. so everything in the queries, completeness, etc travels down the line for validation and linking.
It would be nice to have query options to support these scenarios:
Exists - this should report it exists in either direction
Includes - means downward parent item has an item
Included In - means upward child item is included in an item
not exists - obvious meaning
The same should really apply to completeness rules too. You should be able to check and query in both directions.
That doesn't necessarily tie directly to this discussion but relates.
5
June 09, 2022 17:20
We have "upsell" and "accessories" (item to item relationships) that we would like to export to ensure consistency internally and provide to our distributors externally.
4
July 12, 2022 09:06
Hi!
It would be very valuable if we could export information at several levels, for our busienes, on case on base, case and pallet instead of combine data from different exports which involves risks of doing wrong.
1
September 26, 2022 13:21
Hi inriver,
As we can see in this ticket and the number of upvotes this feature is very important/useful. When can we expect this feature in inriver or will this feature not be build in inriver as this ticket is already from 2019.
Thanks.
Kind regards,
Simon ter Schegget
2
October 18, 2022 17:52
We also need this feature. Was anyone able to find a way to do this?
1
October 19, 2022 11:16
The native inRiver functions were improved earlier this year (incoming and outgoing links are now supported). But they still do not allow all of the functions that are requested above.
I created an HTML extension which allows levels of any (including same) entity links to be navigated and exported.
1
October 19, 2022 11:30
Sounds good! Can you share the HTML with us?
Thanks.
Kind regards,
Simon ter Schegget
1
October 19, 2022 11:36
Unfortunately not, it remains property of my employer. It did take a significant development effort!
Highlights are:
* Runs client-side (there are pros and cons about this)
* Retrieves information via REST API
* Outputs an XLSX file suitable for importing back into inRiver
* XLSX file is compatible with the standard inRiver export format
* XLSX file has coloured indicators for unique fields and CVL keys&values
1
October 19, 2022 14:27
Hi Mark,
No problem, I can image that. Thanks for your solution description and highlights.
Regards,
Simon
1
June 01, 2023 16:44
We also need this feature. It would nice to have this feature since it was suggested a long time ago!
3
September 15, 2023 13:25
We would really appreciate this feature as well!
1
September 20, 2023 16:52
We really need this feature as it seems so do many others based on the 70 up votes since 2019. We need to export item to item relationships since we use these relations for both accessories and related items on our website and in our syndications.
inriver, any updates on whether this is a feature that will be coming?
Thank you.
Not being able to export data from inriver goes against the core values of inriver. Without this, the core function of inriver is not fully functioning. This is not a nice-to-have, but a critical must have, please prioritise.
This is very useful - if not essential - for exporting Channel structures. By exporting Node => node relationships, it is then possible to rebuild the Channel in another environment through the import adapter.