Is it just me? This is literally driving me insane. I set the label on my text box:
Then I preview:
What the heck Epicor???
Is it just me? This is literally driving me insane. I set the label on my text box:
Then I preview:
What the heck Epicor???
I know I should report this to support and find out if there is already a PRB for it but I cannot bring myself to even log into EpicCare anymore, I give up.
And its so inconsistent, here is it correctly labeling some fields and not others, all bound to the same custom view. WHY!!!
I can’t answer the first issue, but the text-area control has a different label style that allows it to float (or not if disabled). I find it rather annoying myself.
Drives me nuts too. If you have a grid for any updatable BAQ dataview you can’t seem to control the label within the grid cell either. Simple checkbox fields need to be extra wide to accommodate the checkbox and label.
I’ve experimented with setting control labels with property set events. I’ve had limited success. I can get the label to change, but only after an event where the dataview has already changed and the original label is visible first. Haven’t found an event that will just set the label on load of the screen.
It’s maddening this is even necessary. Its so basic to be able to label a control, how on earth does this get released in such a state?
Yeah that is annoying but not the issue, the issue is the label is supposed to be Ship SPACE To not ShipTo
Oh damn, didn’t even notice that!
lol maybe my users won’t either. Its driving me crazy.
I can’t replicate that in 2023.1 or 2023.2.
I’m testing in 2023.1
I’m also seeing this in 2023.2, did you ever find a way to make it use the “Label Text” instead of the DB field name?
I’m seeing this now on 2023.2.6 … would be interested to know if anyone has found a solution
On a custom Kinetic app, the first response from the BAQ leaves all my labels where they belong … then the second time the BAQ is executed, all the labels become my BAQ labels - which I can change to be what I want them to say, except the ones I want to have no label at all…
Nope, just have to live with it. I still see it happening intermittently in 2024.1.
Any better in 2024.2? I just noticed this today (on 2023.2).
Yep, that’s what I see also.
Also, did anyone report it?
Support says they can’t reproduce it. Asked for my layer which I provided, which they say they are unable to import. Been going on for months. I despair. Issue still exists in 2024.2.
I think @jwphillips has the key to this: it works the first time, then glitches the second time. I feel like it is reproduceable.
I can’t picture a use case for that, but yeah, that sure would be one thing you could not outsmart with the BAQ.
When you hang the label on the container
I have a label for Address, then the three Address1, Address2, Address3 text boxes below it
Ah, I can see that!