You will probably do a Homer Simpson D'oh, but if you are pushing a button on the parent record then it's the [Record ID#] of the record you're sitting on that needs to be pushed into [Related Parent]
"&_fid_15=" & URLEncode([Record ID#]) &
Hello Mark,
So it is the connection from the parent table to the child. In the relationship, the Parent record ID on the child table is fid_15 which is the [Related Client], fid_18 is the [Client] name. Exposing the formula I'm getting either a 0 or (&_fid_15=&) or (&_fid_18&) into the next string.
The [Related Client] is the numeric reference in the relationship. Which I would think is the right field to use. That worked in my other API button. The fid's are on the child table.
I am on the parent table when clicking the button to populate on the child table. Does the order for fid's matter for API?
If I hard code the Client's record ID # into fid_15, the call works perfectly. When I use [related client] the code says 0.
Qrew LegendYou will probably do a Homer Simpson D'oh, but if you are pushing a button on the parent record then it's the [Record ID#] of the record you're sitting on that needs to be pushed into [Related Parent]
"&_fid_15=" & URLEncode([Record ID#]) &
Hello Mark,
Sir, Thank you very much. I have been so flustered by this formula. Yet again, you have helped me through my challenge. Have a great day, sir!
