1 of 1 people found this helpful
the A-B-C rel tunnel will use the first value in the A-B relationship; just an extension of what is the default value of parsing a related field? - A: the first value of the rel
script it. Don't need a new window, can use a go 'hidden' layout
go bts_customersites, new record, set SiteContacts::site_id set SiteContacts::contact_id, return
this will be invisible ordinarily
I have been able to make this work, however it annoys me that the layout
Here is how I did it..
While the immediate problem has been solved (thanks again) the portal goes
a little crazy as it comes back to the layout, and re-enters the portal.
The layout has also has a script trigger that fires on entry.
Is there another possible solution?
TO Question2.JPG 90.3 K
You could use a dedicated ACRR (allow creation related records) rel: g_site_id = SiteContacts::site_id and g_contact_id = SiteContacts::contact_id
script parse the key values into the two globals : g_site_id and g_contact_id, that way it does not need to leave the layout
Why does the the cursor need to re-enter the portal?
Step through the script using Script Debugger and look for the blink inducing point; probably something the layout script is doing; like a refresh|flush
The flicker can be more of an issue on windows boxes/networks; do not usually see it on Macs
You are so right.
As a part of a layout based script trigger I was clearing a global field and refreshing the window with flush cashed join results enabled.
As soon as it was disabled, the flicker went away.
I did not attempt the other technique, but will once I understand it better.