Header labels disabled in edit mode

Hi guys,

I’m wondering if the following is a bug, but it certainly is an issue for us :)
There is a tableview form that doesn’t have a body or header but there are elements on it, labels, some are independent, some are ‘labelFor’ kind of labels.
So when the form is loaded the ones that are ‘labelFor’ automatically go in the header created by Servoy.
Those labels have actions attached to their onAction event handler, so when I click on a label in the header the action is triggered.

The form also has fields and their labels that are created dynamically at load time.

Everything works like a charm until onRecordEditStart() is called for that particular form.
One of my labels in the table header is to add a new record on this form.
So when I hit it the first time, it’s ok, my method is fired, a new record is created.
But I cannot click the label again before I save or cancel the changes - so this is the problem.

I don’t enable/disable my labels anywhere in the code, it happens automatically and I think Servoy handles this because the sort on the header labels is also disabled when there are unsaved data.
Is it normal behaviour?
I understand the reason for disabling the sort, however, I’d like my labels to work otherwise.
Please comment.

Update: if I have the header part on my form at design time and put my ‘labelFor’ labels on it, then my label works despite there are unsaved records.

Cheers,
Maria

that is currently by design yes, that everything on a table header column is only allowed when there are no edited records of that foundset.
Open up a jira request so that an onaction could be triggered even if there is an edited record

jcompagner:
that is currently by design yes, that everything on a table header column is only allowed when there are no edited records of that foundset.
Open up a jira request so that an onaction could be triggered even if there is an edited record

Hi Johan,

I can’t find an open request for this one, so here you go, I created a new one: SVY-3326
We want this pretty badly because all of our grid-view forms are based on this functionality.

Cheers,
Maria