Jump to content

Go To Related Record Not Working As Expected


GisMo

This topic is 3078 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I've got a simple relationship. Customer->Order via customerID as a foreign key in Order table. Typical operation, I want to jump to the record that I click on from the portal row.

When I put a simple button with a script step Go To Related Record on the portal row it works properly.

When I create a script with GTRR and some other steps in there attached to that same button, it always brings me to the wrong record. I've even tried grabbing the OrderID from the portal row and performing a search, but it always grabs the wrong Order ID. I've experienced this before, but I can't remember what I did to fix it. 

 

Any ideas?

Link to comment
Share on other sites

When I create a script with GTRR and some other steps in there attached to that same button, it always brings me to the wrong record.

Your question would be a lot easier to answer if you had spelled out those "other steps in there". As it is, one can only guess that one of them takes you out of the clicked portal row. Or perhaps you're going to the wrong TO of the child table.

 

I've even tried grabbing the OrderID from the portal row and performing a search, but it always grabs the wrong Order ID.

Same thing.

  • Like 1
Link to comment
Share on other sites

The scripts are all correct. I forgot to mention, my script does "commit records" before GTRR.

In order to make it work, I had to:

  1. grab the ID(Set Variable) of the portal row record first,
  2. commit records, <-calling this before a GTRR in portal
  3. new window,
  4. go to layout
  5. perform find $orderID
  6. Exit Script

I suppose I could also do:

  1. Set Variable Get(ActivePortalRowNumer) $portalRow
  2. Commit Records
  3. Go To Object "My Portal"
  4. Go To Portal Row $portalRow
  5. GTRR...
  6. Exit Script

Any thoughts on performance of either?

Link to comment
Share on other sites

Yes, well the Commit[] is a problem. Once you commit, that portal row now longer has focus so the rest of the script doesn't "know" that's the row you want.

You could do the find. That's my general preference over GTRR. But you could simply take the Commit[] out. If you've edited the record (parent or child) and GTRR with a New Window[] that might record locking issues.

 

Link to comment
Share on other sites

Yea. It threw me for a loop and I was working late last night. I need the commit because I was getting some locking issues(301) when trying to write back to the Customer Table from the context of the Order table. 

Link to comment
Share on other sites

suppose I could also do:

  1. Set Variable Get(ActivePortalRowNumer) $portalRow
  2. Commit Records
  3. Go To Object "My Portal"
  4. Go To Portal Row $portalRow

Well, theoretically after the Commit[], in a sorted relationship/portal the portal rows could be in a different order, due to whatever changes you just saved, so that now the same rowNumber would be a different record … 

Link to comment
Share on other sites

I suppose I could also do:

  1. Set Variable Get(ActivePortalRowNumer) $portalRow
  2. Commit Records
  3. Go To Object "My Portal"
  4. Go To Portal Row $portalRow
  5. GTRR...
  6. Exit Script

If you have uncommitted records in the current window, you could use GTRR with the 'Show in new window' option checked.

Link to comment
Share on other sites

This topic is 3078 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.