Replace Lead Entity

(0) Share

Report

Posted on by RaulOcana

8,270

Hi,

I have this LEAD entity with a couple of new custom fields in Production. On the other hand, in a Trial, I created a custom LEAD with some of those custom fields plus others. I want to import from Trial to Production and that my Trial.Lead replace the Production.Lead entity.

Now I know it it not possible, but have you guys any idea to to this? I can't lost my Production.Lead data, but I need this Lead to have all my trial customization.

thanks guys!

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (1)

Verified answer

Hosk on at

Like (0)

Report

You can import the custom entity from your trial. You will need to save it into a Solution, export the solution and then import the solution into PROD.

The custom Lead entity won't replace the production lead entity because they are different entities (if I understand you question correctly). You will have to create those fields on Production lead or import the custom lead into PROD.

If you want the data records to go into the production lead then you could do an advanced find of the entity records in the trial and then import those into PROD.

Was this reply helpful? Yes No
RaulOcana 8,270 on at

Like (0)

Report

Hi Ben,

Let me know if I made myself clear.

A. I have Lead entity on production. This entity has 30 new custom fields. Main form has a new design.

B. I have Lead entity on trial. This entity has those 30 custom fields of production. Main form has a new design, javascript and a couple of business rules.

I need to replace B on A. But I don't want to lose data from A.

Regards!

Raul

Was this reply helpful? Yes No
Suggested answer

Hosk on at

Like (0)

Report

you reply has certainly made it clearer to me.

I'm not quite sure what will happen if you copy the trial entity, are the fields are the same between prod and the trial.

I would perhaps try and create a solution with just the development code (javascript, business rules) to see if you could bring those across.

if the fields are different then the development stuff (javascript, business rules) probably won't work because the names of the fields are different.

I'm not sure what version you are using but if you are on premise then you can back up the CRM database so you could restore that if you needed.

you can also back up the lead data on PROD by doing an advanced find with all the fields you want and then exporting it to excel. This would mean you could import it at a later date if you needed, you could also import this to the trial lead entity and map the different field names.

So I think you have these choices

export the lead to excel, import the trial lead. This may lose the data or it might not. If the data is lost then you can import the missing data with your excel spread sheet.

the other option is importing the development code (javascript, business rules) and then create the forms again.

Was this reply helpful? Yes No
RaulOcana 8,270 on at

Like (0)

Report

Hi Ben,

The problem is that the solution import fails because there are identical names. So as soon it finds a relationship name in the Lead the import stops and notifies the problem. So I need to do like a workaround to accomplish this or at least I think so.

Was this reply helpful? Yes No
Karth on at

Like (0)

Report

Hi Raul,

I wouldn't recommend using a custom entity for Leads. One of the alternatives you could evaluate is to create additional forms for Lead entity with the new attributes. After all, creating an additional 30 attributes might not be as time consuming, when you look at the benefits you could reap in the future.

The reason I would not recommend using a custom entity for Lead is because Lead entity in CRM is one of the core entities, just like Account, Contact, Opportunity, Campaign and Case. These are the entities which contribute to the traditional CRM processes. What if you have used the custom entity for Lead, and now you want to create a marketing list for your leads - you cannot! What if you want to measure the success of your closed loop marketing? - you cannot. You may have to revisit your design then.

If you still want to go ahead and use the custom entity, you will have to rename the display name of the Lead custom entity in your Dev box and import the solution on your production box. That will resolve your issue of identical names.

HTH

Cheers,

Karth

Was this reply helpful? Yes No
Hosk on at

Like (0)

Report

In that case I think you need To export the lead data and try and import this data into your trail, when you can do this you can the import the trail solution into prod, e.g the whole entity and then import the lead data

Was this reply helpful? Yes No
RaulOcana 8,270 on at

Like (0)

Report

Hi Karth,

I'm using the default Lead entity, I failed at say Custom Lead, it is the system LEAD but customized.

Was this reply helpful? Yes No
RaulOcana 8,270 on at

Like (0)

Report

It seems like the solution that I import, tries to update the Lead entity (in this case) so if it finds the same custom fields it will show me an error. But if I let my trial Lead with my custom fields only it works!

Thanks guys for helping me!

Was this reply helpful? Yes No
Hosk on at

Like (0)

Report

If we helped you please tick one of the replies as the answer that would help me

cheers

Ben

Was this reply helpful? Yes No

Community site session details

Replace Lead Entity

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates

Community site session details

Replace Lead Entity

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

Featured topics

Product updates