It would help if you could elaborate on how many dimension and the form design. But you basically want to identify the Point of View ( POV i.e. The intersection of all the members of dims) at Row 2 of Form A and load that value to POV of Row 8 in Form B. you could write a business rule to write a simple mathematical equation of Row 8 = Row 2. See below an example
Row2 fy18 sep Account1 entity1 actual 100 Row8 fy18 sep Account2 entity1 budget
Your Business rule should basically calculate something like :
Fix (Budget, entity1, fy18,sep)
Account2 = Account1->Actual;
1 person found this helpful
This question has already been asked as part of another one by you. I would repeat my answer here.
Is there a need to create a different account for form B? Can you not re-use the account from form A (either share that member under form B hierarchy or just include one row with this member from form A)?
You are not allowing input in it anyway and making it read-only.
How do I share the member under a form hierarchy ?
Also, how do I include one row this member from form A ?.
I think you are missing the underlying principal here.
Data is saved to the database against a combination of all dimensions' members.
If two forms reference the same combination of data then they will both see the same data.
It is that simple.