Skip to main content
Open

Ability to preconfigure import/export/mass update settings

Related products:Software FactoryWindows GUIUniversal GUIIndicium Service Tier

When screens are configured for import, the default Import functionality is in most instances used in the same manner between different imports (and in many cases the import Excels follow a predefined format).

As a result end users often find setting up the options on the “Select location of column names and data” part of the import wizard somewhat complex and cumbersome.

If the options under “Headers” and “Data” could be preconfigured on subject level in the SF model + an option to skip the entire “Select location of column names and data” (for cases where only one worksheet is used in the import Excel and no data selection is necessary) could be made available, this would make the import easier and quicker to use. 

Forum|alt.badge.img+15
  • Superhero
  • September 29, 2020

Maybe a bit similar to

https://community.thinkwisesoftware.com/ideas/default-import-to-translations-and-retain-to-next-session-1188

?

As far we can notice end users don't understand the concept of ID's / translations, way to difficult. Should be translations by default, and for the advanced users ID's could be used.


Jasper
Superhero
  • October 30, 2020
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/default-values-in-gui-functionality-importupdate-1191
All the votes have been transferred into this idea.

Jasper
Superhero
  • October 30, 2020
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/ability-to-hide-fields-from-importexport-functionality-1433
All the votes have been transferred into this idea.

Jasper
Superhero
  • October 30, 2020
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/default-import-to-translations-and-retain-to-next-session-1188
All the votes have been transferred into this idea.

Jeroen van den Belt
Administrator
Forum|alt.badge.img+8
Updated idea status OpenOn the backlog

Jeroen van den Belt
Administrator
Forum|alt.badge.img+8
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/let-user-preferences-remember-export-options-1783
All the votes have been transferred into this idea.

Forum|alt.badge.img+15
  • Superhero
  • March 17, 2021

I've received some feedback from end users not understanding the whole “ID” concept. It's very difficult to explain and actually, they don't need it at all. It's more of an advanced feature.

Is it possible to hide the “ID's” at all? In both import and export? This could be an user setting in IAM (under UP Availability for example)

 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/disable-certain-columns-from-exporting-and-if-exportable,-provided-with-at-least-a-db_column-header-3156
All the votes have been transferred into this idea.

Mark Jongeling
Administrator
Forum|alt.badge.img+23
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/option-to-disable-update-existing-records-in-import-3680
All the votes have been transferred into this idea.

Forum|alt.badge.img+14

I would also like to be able to limit the columns for a mass update.  


Mark Jongeling
Administrator
Forum|alt.badge.img+23
The following idea has been merged into this idea:
https://community.thinkwisesoftware.com/ideas/allow-to-exclude-columns-from-export-in-sf-5335
All the votes have been transferred into this idea.

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • January 2, 2025
On the backlogOpen

Arie V
Community Manager
Forum|alt.badge.img+12
  • Community Manager
  • January 2, 2025

Status updated to better reflect the Status of the Idea with the clarified Statuses as explained in the Reply here: What happens to your ideas? (updated as per november 2024) | Thinkwise Community



Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings