10.2.100 Upgrade Data Model Error

THOMASDOLBY8-425x320

1 Like

No sir.

The issue is that ExcludeTables will exclude… tables. It does not work for excluding views. That’s why the workaround I suggested didn’t help.
So Nathan’s workaround is the way to go or wait for an upcoming update that will include this fix.

May I throw out the possibility of being able to add views from within the Entity Framework?

:wink:

u can use the external BAQ’s to get “VIEWS” into Epicor @Mark_Wonsil

SaaS user wonders what is this trickery External BAQs?

:wink:

Ugh SaaS … Ugh :face_vomiting::face_vomiting:

Oh, it’s not that bad. Constraint is the mother of creativity after all…

:smirk:

The views that you add to your database can be included in the data model.

For cloud users?

:wink:

Working on that @Mark_Wonsil. The issue is known safe harbor

1 Like

Epicor 10.2.200.5 did not either. The “schema” still exist.
Also the Exclude Table idea did not work either.
Anyone else having this issue?

@e10user I had to actually delete the view to get the data model to regen.

Thanks @hmwillett. We did try this idea.
However, we would have to remove and re-create our database views every time we regenerate our data model for Epicor 10.2.xxx.
All our database views are currently working flawlessly in Epicor 10.1.xxx.
Are you currently utilising this workaround in your production environment?

We’re not on 10.2 in production yet.
Fortunately, for us, the view was no longer required, so we just got rid of it entirely.

Thanks @hmwillett!
We will have to wait.
Our upgrade is not possible until we can test out Epicor 10.2.300 (hopefully bug has been resolved).
Will update this thread once we know more.