Populate reference field from another another scoped app. with BR

Mimmi
Tera Contributor

‎10-25-2019 05:41 AM

Hi,

I have a table containing records of stores in the global application and i have a table in a scoped application containing records of contracts related to specific stores. I want some field values in the contract form to be populated from the store table. I want to do this with a on-change business rule on the store table. 

The thing is that i can't seem to connect the tables in my business rule. I understand that I have to connect them with a value that is the same for the two tables. There are already BR's on the contracts table that populate values on the stores table. In those cases the BR's connect the tables with a reference field on the contract table and a string field on the store table. I believe that's what doesn't work when I try to do the other way around, since the store table doesn't have a reference field value that is a string field value on the contract table. 

This is an example of a BR doing the same thing but in the other direction:
find_real_file.png

And this is my BR trying to do the same but from store form to contract form.

find_real_file.png

I understand this is confusing, but if anyone can help I'd be very grateful!

Labels:
0 Helpfuls
  • 1,798 Views
2 REPLIES 2

Chavan AP
Kilo Sage

‎10-25-2019 06:49 AM

Hi There,

 

Under System Applications, go to Application Cross Scope Access.

 

You should be able to create a record like this one, it should allow the user table to be available in your scope. 

 

find_real_file.png

 

 

If this resolves your query, please mark my comments as correct find_real_file.png and helpful  find_real_file.png.

Regards,

Ajay Chavan

My Community Articles

LinkedIn

Glad I could help! If this solved your issue, please mark it as âś… Helpful and âś… Accept as Solution so others can benefit too.*****Chavan A.P. | Technical Architect | Certified Professional*****
Preview file
2 KB
Preview file
1 KB
0 Helpfuls

Mimmi
Tera Contributor
In response to Chavan AP

‎10-28-2019 03:56 AM

Hi, 

I don't believe this is my issue since I've already given access to the table. But I believe it has something to do with the content of my business rule. Maybe I have to add a query instead of saying 'current.***' since it's not the store table that has the reference value I want to connect the tables with? 

In the business rule that goes the other way around the connection is made by writing 'current.u_store_name.sys_id' and I want to make the same connection but in the opposite direction. To be able to do that I might have to use an addquery?

0 Helpfuls