openTable issue

spinner_7580
2 mths ago
40replies
Answered

Hello -

openTable script stopped functioning.

Starting with 3.15 I have button scripts that direct the user to a table and view

openTable("Supplier", "Inventory") .... has been working for months.

When the button is clicked the Supplier table is brought into view but not the Inventory tab. It defaults to the first tab in the table rather that the one in the script.

Any ideas?

Scripting and Functions

- Mel_Charles
- 4 wk ago
- Reported - view
With the release of 3.15.3 public web version the popup issue seems to be resolved !
- spinner_7580
  
  3 wk ago
  
  Reported - view
  openRecord() not resolved on 3.15.4 Public Cloud and Mac app
- Fred
  
  3 wk ago
  
  Reported - view
  I just tried it on 3.15.4 (public cloud) and 3.15.2 (MacOS) and openRecord() worked for me.
  
  The first part of the video shows the record in Table2 with a tab called Jump. Then I switch to a Page, then click on a button with the following code:
  
  let x := first(select Table2 where Id = 2); openRecord(x, "Jump")
  
  You can see it opens a record and takes me to the tab called "Jump".
- Rafael Sanchis
  
  Rafael_Sanchis
  
  3 wk ago
  
  Reported - view
  I Fred yes work too on 3.15.3 on Android.
- spinner_7580
- 3 wk ago
- Reported - view
Obviously I'm not grasping something fundamental here.

I notice in your video that you get a "popover" window when the script goes to your Jump tab. That is not the desired UI behavior I have been getting prior previously.

In other words, I just want the page/tab view to change, i.e., no popover, which used to work.

I've uploaded my sample DB. I created a button with your script next to my sample button to show the behavior on my end using MacOS 3.15.4 ( switches to Destination table but not Destination Tab )

Also, I don't understand why you added the Id reference in your script - doesn't the first operator indicate/imply Id=1?

My sample button doesn't use the Id reference and mirrors the script format that I have been using successfully previously.

kind regards...

openRecord issue - sample
- Fred
  
  3 wk ago
  
  Reported - view
  Try moving the "all" table view to be the first view in the "Destination table" table. The Destination view in the same table is a form view and thus does not seem to allow Ninox to switch tabs.
- spinner_7580
  
  3 wk ago
  
  Reported - view
  Thanks for the suggestion - tried that but still doesn't switch to the desired tab.
- Fred
  
  3 wk ago
  
  Reported - view
  The Destination form will never switch. It should open a record from the all view then switch to the Destination tab.
- spinner_7580
  
  2 wk ago
  
  Reported - view
  What you are suggesting is a potential workaround for the malfunctioning openTable() command - which I submitted as a bug.
  
  Using the openRecord() command is a possible workaround but just not for my application. I used the openTable() command to switch to a tab that displays a dashboard function so having the popover behavior isn't ideal for the users. Thank you for your advice!
- Fred
  
  2 wk ago
  
  Reported - view
  Are you talking about openTable() or openRecord(). They both work for me. I just tried openPage() and that didn't take me to the specified tab (public cloud 3.15.4).
- spinner_7580
  
  2 wk ago
  
  Reported - view
  This thread started out re openTable. You suggested openRecord as a workaround. Your workaround using openRecord() does work just doens't suit my application.
  
  openTable() is broken for me in Mac app 3.15.4 and the public cloud. I submitted a bug report re openTable()
- Fred
- 13 days ago
- Reported - view
said:
openTable() is broken for me in Mac app 3.15.4 and the public cloud. I submitted a bug report re openTable()

I just tried in 3.15.2 of the MacOS app and 3.15.4 of the public cloud and openTable() it worked for me.

openTable("Table2", "Form")
- spinner_7580
  
  11 days ago
  
  Reported - view
  In your example when you are clicking on Page1 in the sidebar -- I have not played with that feature yet.
  
  However, my goal ( which used to work ) would be, in your example above, when you click on Page 1 in the sidebar and then click the Button in Page 1 the result would be to go to Form but select the Jump tab in Form instead of the Table2 tab.
  
  By used to work I mean being able to navigate to any table and any tab in that table without the popover behavior.
- Fred
  
  11 days ago
  
  Reported - view
  said:
  then click the Button in Page 1 the result would be to go to Form but select the Jump tab in Form instead of the Table2 tab.
  
  So you used an openTable() command to go to a tab in a record?
  
  If you did then that would be a bug since openTable() should only go to tables then views of a table. :)
- Ninox partner
  
  RoSoft_Steven.1
  
  10 days ago
  
  Reported - view
  Haven't tested it but if there are no table views and only one Form view. Wouldn't that be the case it used to work in the past?
- spinner_7580
  
  8 days ago
  
  Reported - view
  Yes, earlier in this thread you had pointed that out to me. Honestly I don't deeply understand the relationship between tables/views/tabs/pages/forms
  
  I must have fooled myself when I ended up using the opentable command in conjuction with openrecord to get to the table and tab desired.
  
  So, when 3.15 showed up it broke the ability to get to a table/tab without the popover effect.
  
  Now when users click the button, that would previously take them to a particular tab, they now have to look at the tabs and click the correct one. A fairly minor annoyance after a bit of training to be sure but it's just not as smooth as it use to be and should be... I guess I'm whining a bit as a result of many yrs of FMPro work where there was a lot of functionality for creating desireable UI design.
  
  Thanks!

Welcome to the Ninox community

openTable issue

40 replies

Content aside

Categories

Overview