Table does not exist error

(0) Share

Report

Posted on by Community Member

Hello guys,

my project has model that extends Application Suite package, but in the same solution I have to customize different package, so I created a project with different model that extends that Directory package. The problem is that this second project has table (DirPerson) that references to other (CustomMade) table, but DirPerson cannot see it as I build the solution and throws an error. Do I have to deploy it in someway or what? Thanks in advance for your ideas.

*This post is locked for comments

I have the same question (0)

All responses (16)

Answers (1)

Suggested answer

Basheer17 2,720 on at

Like (0)

Report

You can't customize Directory model elements from your extended model in Application Suite. You can create extensions but for overlayering you have to create new model in the package where you want to customize.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yes, I created new model and used it in other project in the solution

Was this reply helpful? Yes No
Basheer17 2,720 on at

Like (0)

Report

Update the model parameters, set reference for the model wherever your CustomMade table is residing.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

But table from one project cannot see the table from other, how could I fix that?

Was this reply helpful? Yes No
Basheer17 2,720 on at

Like (0)

Report

You must have created a new model for creating relation between DirPerson and CustomTable. Update the model parameters for the model that you have created in Directory Package.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I updated the Directory package model to refer to all existing other models, but the error is the same :/

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Path: [AxEdtInt64/ASC_HcmEmployeePFA_DOS/ReferenceTable]:Table 'ASC_EmployeesPFA_DOS' does not exist. HDD_FieldsMappingProjectsDir_DOS (VAR) [Overlaying Package HRMFDD Directory]

It seems that it tries to look only in the Directory model, doesn't find it and throws it.

Was this reply helpful? Yes No
Martin Dráb 237,801 Most Valuable Professional on at

Like (2)

Report

I'm struggling to understand how your packages look like. When you say that you extended a package because you need a customization, it sounds like a contradiction to me.

Do you have separate packages with references to standard packages (extensions) or did you put your models to existing packages (customization)?

Was this reply helpful? Yes No
Martin Dráb 237,801 Most Valuable Professional on at

Like (2)

Report

The model name in your last reply suggests that it's a customization. I'll call it Model2 - it's inside the Directory package, correct?

What about your first model?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

I have a solution with 2 projects: first one uses a model that extends Application Suite package, the other project uses a model that extends Directory package.

Was this reply helpful? Yes No