omar:
I have no idea how this is possible. No other option than to revert back to a previous version until somebody else has the same issue or it is fixed…
Did you download this version:
https://github.com/Servoy/servoy_jasper … 12.0_7.0.1
I added a line of code to make the tab visible, even though the visible property isn’t changed anywhere in my code, the forms display more often than not. However when you scroll through the foundest still get the “loading” message which never disappears.
from the server log
Warning: Change sent from client to server for property ‘myFoundset’ with data ‘[{“newViewPort”:{“startIndex”:0,“size”:150},“id”:128}]’ of component ‘stock_table’ was denied (blocked by property named ‘visible’).Block reason: Parent container ‘stock_list’ of this component ‘stock_table’ currently blocks incoming client changes because of parent container property: visible
then
16:23:16 ERROR DataGrid - Could not load records for foundset root Start 50 End 100 buildStackMessage@http://localhost:8183/chunk-VZHH4OTU.js:29665:24
apply@http://localhost:8183/chunk-VZHH4OTU.js:29460:53
@[native code]
@http://localhost:8183/chunk-VZHH4OTU.js:142710:32
timer@http://localhost:8183/polyfills.js:1459:32
runTask@http://localhost:8183/polyfills.js:145:47
invokeTask@http://localhost:8183/polyfills.js:408:33
as I was scrolling through the foundset both the form and Ng Grid (‘stock_table’) were visible.
Just to add to the ‘blocking’ issue Richard & I are discussing, the problem only happens (for my solution) if you go from a table/grid view to a normal form with the new record.
I just added some code to my solution to allow creating a new record straight from dashboard and that doesn’t make ‘block’ WARN happen
function onActionNewDonor() {
scopes.global.showForm(forms.contactTableView);
application.sleep(500);
forms.contactTableView.newRecord();
}
and even though in theory the Table View should be shown, it actually isn’t, but the ‘history stack’ thinks it was, so that when ‘Back/Apply’ is clicked, it goes back to the correct table view for that new record type & not the dashboard…
sanneke:
omar:
I have no idea how this is possible. No other option than to revert back to a previous version until somebody else has the same issue or it is fixed…Did you download this version:
https://github.com/Servoy/servoy_jasper … 12.0_7.0.1
Absolutely. Two times already, I am going to follow Marc’s suggestion, do a new install and build up my project again. That should work I guess.
Have changed from a Servoy tab panel to the Bootstrap tab panel and so far the forms are displaying, can scroll through all the records.
We need a case with a sample that shows this blocking stuff, else we can’t do much because we don’t know how that can happen.
We don’t see that in any of our (e2e) tests that we run
rafig:
And whilst I’m reporting issues, there is also a problem that updated components, like Bootstrap labels, are not having on ‘spec’ stuff removed from them.
I had to clear loads of warnings in my solution where these properties where left
faclass (replaced by imageStyleClass)
alignment (no longer used)
styleclass (replaced by styleClass)
There may be others, but these happened the most for me.
[I actually fixed them by opening the frm’s in BBEdit (text editor) and deleting those lines & saving & Servoy noticed the ‘fix’]
[attachment=0]ScreenFloat Shot of Servoy Developer at 13 Jan 2025 at 15_16_59 Large.png[/attachment]
Please can you fix these problems ASAP???
ThanksRafi
what component is this that you talk about here?
is that bootstrap DataLabel? but that one never had as far as i know “faclass”
jcompagner:
what component is this that you talk about here?
is that bootstrap DataLabel? but that one never had as far as i know “faclass”
The ‘Label’ Bootstrap component.
It’s really easy to see, install latest Servoy, import the ‘Sample Application’ in Web Package solutions and look at all the Warnings for the solution…
Thanks
Rafi
ah but that should be for the most part quick fixable. '(but i see for some there is a problem with that, exceptions is show in the log)
jcompagner:
ah but that should be for the most part quick fixable. '(but i see for some there is a problem with that, exceptions is show in the log)
Firstly, Doh! didn’t think to use ‘Quick fix’!
But…
When I did use it, it got “stuck” or stopped working (even after re-launching Servoy Developer) & would not clear the faclass property in the ‘chart’ forms… [dialog would not do anything on clicking Finish button & warnings didn’t clear]
[attachment=0]ScreenFloat Shot of Servoy Developer at 21 Jan 2025 at 14_44_01 Medium.jpeg[/attachment]
so maybe that also needs fixing
yes for that one i created case: https://servoy-cloud.atlassian.net/browse/SVY-19934
its related with form/element extend (having a super element )
Thanks!
We are looking into that regression related to visibility & change denied: https://servoy-cloud.atlassian.net/browse/SVY-19938
Andrei Costescu:
We are looking into that regression related to visibility & change denied: https://servoy-cloud.atlassian.net/browse/SVY-19938
Thank you!
I really hope you can sort this quickly…
I found the change in datagrid that triggers these error messages (datagrid requests now a viewport change due to the new record that is being inserted; but as the same request also changes visible form, that data viewport change request is blocked both on server and cancelled on client - as both see the old table form as hidden then => the error messages); we have to think of an alternate fix that doesn’t cause this. Anyway, this doesn’t seem to affect functionality of the cloud sample solution.
But I have to see if I can reproduce Richard’s problem as well - that the grid was no longer working correctly when using legacy tab-panel (but not with bootstrap tab-panel).
I really want to see if it’s the same cause.
@Richard1521662995 I tried to reproduce what you are saying but can’t (tables not working properly).
Please create/attach a small sample solution that shows this to the case: https://servoy-cloud.atlassian.net/browse/SVY-19938
HI,
Have added this line to my servoy.properties file, but each time developer starts the line ‘disappears’, guess Servoy I deleting it. On the Servoy Admin Page I can’t find a setting for servoy.foundset.deleteWithAutosaveOff. Where do I go to set this?
Thanks.
Did you adjust the properties file when servoy was running? Make sure you don’t do that
Hi Johan,
Made the change when Developer not running and all OK now.
Thanks.
Richard