Mapping help - fields not populating

[matthu]

Hi everyone. 

I have an issue with field mapping in my model-driven app. 

I edited the "email" table and added some fields to a form.

I field mapped from my custom table to the new email fields in DEV.

When I went to the timeline on a form in my custom entity in DEV environemnt the mapping worked perfectly.

I packaged the email table in a solution and exported it to my TEST environment.

I exported the latest version of my custom entity into my TEST environment.

In my test environment the mapping doesn't work. 

Any help would be greatly appreciated from anyone. 

Matthu

[matthu]

Note in point three above, where I mention the timeline the mapping should occur after I select the plus button and open a new email form, but it doesn't.

[wwweber · Accepted solution]

Hi @matthu 

I don't know if you are still looking for a solution to this. But if you are I have a question about the method for moving the tables between environments. 

Are you moving the tables as two separate solutions?

And if so, are you sure that you have the relevant relationships, including the mapping, as part of the solution?

The reason I am asking is that I would recommend packaging both tables/entities as part of a single solution, containing the relationships and the entity mapping which would allow this function to work properly. 

[matthu]

Hi @wwweber ,

Thank you for taking the time to reply. You are correct, I was importing these two tables in different solutions. I thought I had everything correctly configured. Both solutions existed in DEV and my TEST environment is identical to my DEV environment so I don't know why it would not work?

I ended up adding the email table to my main solution where the other table already resided and export imported that, then it worked. To aide my understanding does the relationship and both tables HAVE to be in the same solution? Or have I missed something around how I should of set this up if the two tables are in different solutions?

I really appreciate your input.