web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Attribute new_region is a Picklist, but a Lookup type was specified.

(0) ShareShare
ReportReport
Posted on by 790

dear all

on production, i do have a field called "new_region" which is a optionset.

i did some modifications on sandbox and this became a lookup field (on regions entity) instead of a static optionset.

when i did export/import from sandbox to production, import failed with an error "Attribute new_region is a Picklist, but a Lookup type was specified." 


now, i dont understand how the solution expects me not to change such field, and what is the use of export/import if such simple field change can fail a whole import process.

in addition, and even if i think to change it manually (on production) to be lookup field, too many dependencies are there, also i do have many similar changes or even more complex ones, those also will fail and fixing them all manually is almost impossible.!!!

any help please?

2018_2D00_09_2D00_17-02_5F00_32_5F00_10_2D00_importlog_5F00_HS_5F00_1_5F00_0_5F00_0_5F00_0-_2800_3_2900_.xml-_2D00_-Excel.png

thanks,

*This post is locked for comments

I have the same question (0)
  • Ahmad Saud Profile Picture
    790 on at

    one thing to add, the new lookup field (region) is referring to a whole new entity that is part of the sandbox and not yet created on production, that is why i am trying to export it/import it to production.

    so even if i want to modify the field type to be a lookup field that is referring to "region" entity, i can't, because the entity "Region" does not exist on production, but exists on sandbox.

  • Verified answer
    RaviKashyap Profile Picture
    55,410 Moderator on at

    Hi Ahmad,

    How did you change the type pf the field? I don't think its even possible. Did you delete it and recreate it with the same name as lookup type? If yes then this is expected cause when you import a solution crm updates the components ( it doesn't delete and recreate) so while updating it, it is looking fo roptionset field.

    It is never a good idea to recreate a field with the same name of different type if it is already deployed to production. This is because you can have many dependencies, custom code written considering the field as optionset but even if you are able to update it with some unsupported method, ant related code, workflows, business rule will fail.

    Hope this helps.

  • Ahmad Saud Profile Picture
    790 on at

    thanks you Ravi, it is true, i did recreate them with the same names,

    now, do you have any suggestion to fix this issue?

  • Verified answer
    RaviKashyap Profile Picture
    55,410 Moderator on at

    Hi Ahmad,

    Unfortunatly there is no way you can export/ import this with the different type. You can however create new lookup field with different name and then just deploy that field and you lookup entity to production.

    Hope this helps.

  • Ahmad Saud Profile Picture
    790 on at

    thanks Ravi

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans