"Transfer Address Book entries" button on WebAccess
We are using different databases for our different subs. We need to transfer address book records between databases but this feature is not available in WebAccess.
-
Anonymous commented
The sooner you can fix this, the better.
-
Roger Bartlett commented
I would like to see this feature added.
-
Paul Battaini commented
I would add that when reviewing the detailed spec for this feature, the expected behaviours is that ALL associated content below the level of the Transferred entry is brought across. This carries some fairly complex to handle implications, such as variation in UDF structure and even differences in System fields such as Category, Products, Case Resolution and Opp Close Status's to name a few.
Ideally the solution should identify these discrepancies, and provide a mapping with default assumptions presented. This mapping should then be able to be saved/template and even Admin restricted from changes, so that standard users can DO the transfer themselves, but not alter the intended alignment of data.
PS. If full expanded out to allow packaged files for transport, this feature becomes very powerful as it means different Maximizer users could share database records and all use our product, so that businesses that have partnership arrangements could recommend Maximizer as the de facto choice for handling provided records.
-
Christine Sutherland commented
Point #2 of Paul Battaini's comments dated 2 June 2017 is very relevant to us.
-
John Burrell commented
This also needs to be more robust than the current Windows client Transfer feature which often crashes. I had to transfer 1,575 records from one AB to another in the weekend & had to break it down to 10 separate ranges of records to be able to achieve success - very time-consuming & frustrating
-
Paul Battaini commented
The use cases for this are many.
1) One customer with several different operational departments or databases that are managed separately, but can have clients/records that need to move or duplicate between each department.
2) Use of a separate database to Archive records into or back out of, to keep the "main" database simpler to user and maintain.
3) Separate subsidiaries or geo's where records at typically (or even legally need to be) separate but can also be shared or changed to a new "owner" in specific cases.
4) Combining multiple prior databases into the one final/operational database.
5) Splitting one database into new distinct ones for various business purposes, such as provide to another business to operate on, split up of a larger business, etc.
6) Allow Partner type businesses to maintain records in their own Maximizer system and periodically update the parent organisation with the latest information on some or all of those records.
-
Oz commented
No Transfer feature and no Export feature on MX2017 webaccess !
You decided to stop the windows access before adding all the features to the web access ?? -
Oz commented
We have on-premise installation and we use about 10 differents databases for all our subsidiaries.
With MX Windows Client, we were able to transfer records between our databases. Since we use WebAccess, we don't have this useful feature. -
Can you please tell us more details: Are you on-premise customer? what is specific use case? how often do you need to move AB entries? how many databases do you use? thank you!