Why can’t we update these properties while the instance is open and its only shown in the new popup initialization
Also we can’t define it in data variables as well to use it in queries of get !
each popup instance of the popup can be initialised with different properties. Personally I wouldn’t want it to change but what’s your use case? if your changing a global variable why not just bind that?
Somtimes the data is being changed by an action from the user and backend calculation updates as well and we need in this case to update the value of that property and this is within the instance it self opened
Also data to be filtered query by exposing this selected data as we are doing a redundant variable which is local and in the instance it self
Bind the property to a variable, then use that variable to store any of the changes made this will update the property.
2 Likes
yeah but issue is the variable is not even exposed to filter and query with it in the data source, it can’t see it, The idea of exposing these properties are better and only when the instance is on, instead of having a tremendous amount of variables in the local data stored and confusion
Plus it’s a 1 action place to do the update rather than doing multiple steps, which is also, as mentioned, not usable outside the instance
I’m not sure what you’re talking about now to be honest, use a global variable. It works.
The new popups have a separate instance with their own variables, formulas, and workflows within the instance itself. There’s no need to involve global variables, which saves a lot of organizational settings per instance and makes maintenance easier.
Using global variables would work, but the issue is that many global variables would be created, which is the opposite of the new popup instance feature.
What we require is the ability to update the popup instance’s main properties without having to reopen it.
Secondly, we need to be able to expose any of the instance variables, just like we used to do in custom components.
Can you explain a use case. I don’t get how something is changing and you can’t either use a popup variable to save that change, if in the popup. or if your not in the popup use a global variable/collection as its a global change.
something to remember is that you can pass data out of a popup using the on close triggers too that are useful in some cases where you need to reference something that was in the popup
Well thats the issue too many variables sometimes will need to be passed as a global one and in this case if they can expose the variable outside the popup instance while its open then that will be better than.
am not stuck am asking for an improvement.
Unfortunately it’s just not possible atm though and parameters have worked like this for awhile I doubt they’re changing any time soon when there’s a pretty reasonable workable method to keep the parameter updated using a global variable. I suggest you either try figure out a method that works for you using global variables there’s plenty of ways you should be able to only use 1 or only a few global variables for the pop up properties. Otherwise you most likely have to change your whole setup. I wouldn’t rely on WeWeb changing this for the way you want it to work.
1 Like