Invalid 'Table Name' selected on the x Definition record. The 'y' table is in application 'Development Lifecycle Management', but the current application is 'Global'.

suvro
Mega Sage
Mega Sage

Hi All,

I created a scoped application similar to CAB workbench naming ARB Workbench, but the background table we are using here is a table from another scoped application rather than change_request table.

But whenever I am trying to create the ARB Definition record it is giving me the error below:

 

Invalid 'Table Name' selected on the ARB Definition record. The 'DLMS Design Plan' table is in application 'Development Lifecycle Management', but the current application is 'Global'.

 

 

Kindly help me with this. It is running fine when I am creating this record in the Development Lifecycle Management scope, but that is not appropriate user using that application wont be selecting scopes.

1 ACCEPTED SOLUTION

suvro
Mega Sage
Mega Sage

Hi Friends,

 

This issue was resolved by setting allow_public attribute of the field to true.

 

Thanks for inputs, I really appreciate.

 

Regards,

Suvro

View solution in original post

3 REPLIES 3

Lukasz Bojara
Kilo Sage

Hi,

You need to allow data operations from other scopes. There are few things that you schould check when you problem with Application to Application access, so issue with scope.

 

1. How your table configuration look like? Do you allow access from other scopes and what type of access do you allow. Check the Application Access tab on your table configuration.

find_real_file.png

 

2. Go to System Applications > Application Cross-Scope Access and check if you have entries that points from your scope to gloabl scope with Target Name being your scoped table. Example below:

find_real_file.png

 

If my answer helped you in any way, please then mark it as helpful. If this solved your case please mark it as correct answer. Thank You.

 

Best regards,
Łukasz

 

Tried this but no luck. Actually cannot create cross scope from global to scoped application

suvro
Mega Sage
Mega Sage

Hi Friends,

 

This issue was resolved by setting allow_public attribute of the field to true.

 

Thanks for inputs, I really appreciate.

 

Regards,

Suvro