2 of 2 people found this helpful
Hi Alina, it would be helpful to have a couple of screen captures so we can try to reproduce your issues since you have several, I will try to separate your issues.
I) Running validation when using an extension container:
So you have a view (VA) with a record editor A and inside an extension container.
Then you have another view (VB) extending VA with a record editor B.
When you are in VA and you save the record instance A you trigger a rule you created (?) that is triggered on Update and Create. Though it fires immediately before the data on VB is saved (record instance B).
Is that correct?
I think we talked about this with Robert Curlee, to have a trigger "after create of association" but I don't think we have this yet.
A couple of suggestions here. Can you try to:
- Use "AFTER CREATE" / "AFTER UPDATE" and see if it changes something?
- Or try to trigger the rule when record instance B is saved rather than A. From B you can follow up the association you defined between records A and B to find the A parent and do your checks.
II) Current User:
Don't get me started on this... It has been a while I want to see it and it is not everywhere yet Robert Curlee.
There is a "workaround" that we use. You could create a view component to get the value (but that would mean code) or you can have a field that has as default value the $USER$:
III) Foreground forcing keyboard navigation:
Could you show a screenshot?
IV) Missing objects in the extension view:
So I guess what you would like to see if to have more objects available in this extended view? Like buttons etc...?
The idea behind extended view is that they are "just" here for you to enter data.
What would you like to do with the button? Change / set a value for example?