How: Ability for user to select all entities in table view & export with fields already selected as their export configuration. Ability to export with existing fields in table view or add additional fields from entity field list.
Why: Allows users to export data as they were using it in their view and not recreate it again for the export.
For Who: User experience
Impact: Large impact for all users. Saves time extracting only the data they need.
Additional context: They save their personal table views and then have to reselect the columns they have created in those saved views every time they export.
Please, add your suggestion and feedback above to add to the insights used by Product team when deciding priorities and direction of the Inriver PIM.
Additional business case...
Allow Workspace View Columns to Drive Export Field Selection and Enable Shared Export Configurations
Business Case & Proposed Enhancement
Inriver Workspace Views allow users to define and save the specific columns they need to work with for a particular business process, customer, department or use case.
However, when a user selects Export from a Workspace View, the export does not use the columns defined in that View. Instead, all available columns are selected by default, requiring the user to manually select the required fields again.
This significantly reduces the value of Workspace Views and creates unnecessary duplication of configuration.
The fundamental issue is that the View already contains the definition of the information the user has determined is relevant, yet that configuration cannot currently be reused when exporting the same information.
For example, a business may create a Workspace View for a particular customer containing:
Product ID
EAN
Product Description
Brand
Country of Origin
Ingredients
Allergens
Case Barcode
Case Quantity
When the user selects Export, they would reasonably expect those same fields to be used for the export. Instead, they are presented with the full available data set and must manually select the required fields again.
This means the user has effectively configured the same requirement twice.
The additional issue with saved exports
The current workaround is to create and save an Export configuration. While this avoids repeating the field selection each time, it introduces another significant limitation: saved exports cannot currently be shared with other users.
This means that if a department has ten users who all need to export the same customer data, each user may need to create and maintain their own export configuration.
For example, if a business has 20 customers and requires a different export configuration for each customer, this could result in up to 200 individual configurations being created across 10 users, despite the underlying requirement being the same.
This creates a "configure once, recreate many times" scenario.
It also creates a governance problem. Different users may configure the same export slightly differently, resulting in inconsistent customer outputs and increasing the risk of required attributes being omitted.
Proposed enhancement
We would like inriver to allow the columns defined within a Workspace View to automatically drive the column selection for an Export.
When a user selects Export from a Workspace View, the fields defined within that View should automatically be selected for the export.
The user could then either:
Export using the View configuration as defined; or
Add/remove fields before completing the export where an exception is required.
This would make the Workspace View configuration reusable rather than requiring the user to recreate it within the Export function.
Ideally, this capability should also extend to shared Workspace Views and shared export configurations, allowing a business to establish a standard configuration once and make it available to authorised users.
Business impact
The current functionality creates unnecessary operational overhead across several areas:
Productivity
Users spend time repeatedly selecting fields that have already been configured within a Workspace View.
Administration
Teams have to maintain multiple copies of effectively identical export configurations.
Data governance
There is no single, centrally managed definition of what should be included in a particular customer or business-process export.
Data quality
Manual field selection increases the risk of missing required attributes or producing inconsistent outputs.
Scalability
The problem becomes increasingly significant as organisations manage more customers, channels, attributes and users.
Why this is more than a usability improvement
This is not simply a request to make the Export function slightly easier to use.
Workspace Views already represent a business-defined selection of relevant product information. The inability to reuse that configuration for exports means that the same business logic has to be recreated elsewhere in the platform.
Allowing View configuration to drive exports would create a much more logical relationship:
Define the required data once → View it → Export it → Reuse it
Rather than:
Define the required data → View it → Recreate the same configuration → Export it → Ask every other user to recreate it
This would reduce duplication, improve consistency and make existing inriver functionality significantly more valuable.
Expected benefits
The enhancement would provide:
Reduced manual administration
Increased user productivity
More consistent customer exports
Reduced risk of data selection errors
Easier onboarding of new users
Improved data governance
Better scalability as customer and product requirements grow
Greater value from Workspace Views
Reduced duplication of configuration across teams
Most importantly, it would allow businesses to configure their data requirements once and reuse that configuration, rather than maintaining multiple disconnected versions of the same requirement.
Wider customer benefit
This is not an organisation-specific requirement. It is a natural extension of the existing Workspace View and Export functionality and could benefit any inriver customer managing product information across multiple:
Customers
Retailers
Marketplaces
Sales channels
Internal departments
Regional markets
The more complex an organisation's product data model becomes, the greater the operational benefit of being able to define and reuse data selections.
We believe this enhancement would provide a relatively simple but high-value improvement to the existing inriver experience, while delivering tangible benefits in productivity, data governance, consistency and scalability.
The need to manually reselect the columns for each use case results in inefficiencies and reduces overall usability. The system should provide a persistent or configurable column selection to improve user experience and operational efficiency.
I was just about to log an idea for the same so you have my vote.
When you use the Export option in the ... menu you have to redo the attribute & language selections.
When you do the Export to Excel through the context menu, it doesn't recognize the attributes/fields and language so you have to map everything manually.
I would also be in favor of getting the option to copy your attributes&languages when you do the Export through the ... menu, or get it by default (and then you can change it / select all attributes / languages) if you still wan tot export "all".