• If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Announcement

Collapse
No announcement yet.

New AppVars for Features

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • New AppVars for Features

    I am having an issue that may relate to the new nabFeature... app vars.

    I have two applications, written over a year ago in 6.0.
    Think of them as reporting portals.
    They display lists of "reports" (really grids) for the user to select from and see the chosen report/grid.
    Each app governs a different collection of reports/grids.

    In each application, each report/grid is coded with a Feature name.
    The startup programs disable all features.
    The On Click in the report list enables the one feature of the one report/grid chosen.
    The one report appears.

    Both apps have worked fine for the past year.

    I needed to make a behavior change in one app but not the other.
    In Dev (6.1.20220824.0), once I saved the changed app, it no longer behaves as before.
    Now, when selecting one report/grid from the list, ALL reports/grids open.
    Each too small to be seen in the flexed viewspace .

    Using the Portal Admin logging (which I am coming to love!), I can see that my disable/enable features are happening as expected.
    One is enabled, and all the others are disabled.
    But the nabFeature... appvars are all showing as "true".
    Could this be why all my grid widgets are appearing at once?

    The other unchanged (unsaved?) app still works fine.

    Any thoughts?

  • #2
    This is an issue with the new nabFeatureXXX app variables. The issue only occurs after saving your existing application (as you have experienced). This can be fixed by opening your application in NAB and blanking out all of the nabFeatureXXX app variables.

    We have a fix for this on the next update.

    Comment

    Working...
    X