NetTalk Central

Author Topic: Browse buttons need row-click first  (Read 3116 times)

bergsj

  • Jr. Member
  • **
  • Posts: 81
    • MSN Messenger - swjvandenberg@hotmail.com
    • View Profile
    • Email
Browse buttons need row-click first
« on: October 11, 2010, 04:12:42 AM »
Hi,

When I select the edit button (or any other button for that matter) on a browse it does not open the correct record. First I need to click the row, that makes the ID being saved, and then I can click on a button to open the correct record.
This also happens in the examples.

Is there a way around this?

Cheers!
Sjoerd

PS. using PR31
Greetz,
Sjoerd

Bruce

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 11251
    • View Profile
Re: Browse buttons need row-click first
« Reply #1 on: October 12, 2010, 09:22:27 AM »
single component unique key?
same key in both browse and form?

cheers
Bruce

bergsj

  • Jr. Member
  • **
  • Posts: 81
    • MSN Messenger - swjvandenberg@hotmail.com
    • View Profile
    • Email
Re: Browse buttons need row-click first
« Reply #2 on: October 12, 2010, 10:33:12 PM »
Yes, this only happens in two cases;

It happens with all buttons (custom and predefined) when having the form as popup.

When having a 'normal' form than it only happens on the custom buttons where I would use a custom URL and use p_web.GSV('PRE:Id') to get the row ID.

So the SSV(Pre:Id) only happens when actually clicking on the row. I think the 'popup way' also uses p_web.GSV('PRE:Id') to get the ID.

Makes any sense?

Greetz,
Sjoerd