Developer forum

Hi Per,

Could I have you attach the source file as well?

Regards /Snedker

Hi Per,

I've seen your job mappings for importing users, there should be added a constant mapping for AccessUserType column.

Column "AccessUserType" should have a value of "5" for Users import and "2" for Groups import.

We are currently working on the new User Provider that will handle that import.

Regards, Dmitrij

I have attached it to the first post.

Thanks for the quick response.

Hi Dimitri

I am not quite sure what I should do.

I would like different groups that are not present to be made in the import process.

How should my source file be? Please adjust the one I have uploadet and upload againg.

Thanks 

Per

Hi Per,

I think you'er stepping on one of our bad toes right now!  :-)

What you want to do is not possible without you writing your own job using the API. We are aware of the weakness we have when it comes to user handling in Data Integration, so, as Dmitriy stated: we have just finished a User Provider. It has just been wrapped up and is up for testing next week. After our QA we can provide you with a release with this new provider by the end of next, or the beginning of week 44.

If that is all jolly to you, let me know.

Regards /Snedker

Hi Morten
Thanks for your answer. Looking forward to the solution.
The above was my testing and not an actual task for a customer so there is no hurry, although it is needed.

I think it is very important for our customers that imports can be done by them without technical insight.

Therefore I hope that you will provide example source files with all the available field names for user and product import etc.
And a step by step guide for each.

Thanks again.

Best Regards
Per
 

Hi Per,

On a second thought: what you want to do IS possible if you split into two files. Import your groups first, and your users second. When importing users using Dynamicweb Provider you may set AccessUserUsername as the identity column (or any other column for that matter). Only requirement then is that the chosen column holding the group name is unique.

Your file with users would then have a column for group membership, mapped to the column in AccessUser holding the group name.

/Snedker

Hmm.

How should the group list be formattet and which identifyer shold I choose?

What about the comment from Dimitri - is it not needed to do what he wrote?

PS: Where dig my import that was successfull bit didnt show anywhere go? Is it making trouble somewhere?

No, my bad. It all falls back on not being able to point to proper group. The problem is that with current Data Integration you cannot point to a group by name. And since it has not yet been created, we can't assign the user to the group.

Dmitriy is correct in his reply. But that makes no difference when it comes to the group problem.

So: wait up for the upcoming User Provider.

/Snedker