So I have a custom layer on Order entry that basically makes everything read only except for a UD field and promisedate which I’m doing with a Data rule with an except column exemption. Oddly, with this in place the line navigation control is disabled as well.
Any ideas? Even in Order Tracker this control is available.
I’ve tried adding orderline to the columnlist and that didn’t seem to have any affect.
Because Epicor introduces new fields with every update, and there are many sub-tables fields we’d have to do that for.
Where this layer is meant to allow our production folks to maintain 1-2 fields on the order.
Well, then you may have to dig through events to see what triggers the line control to go read-only with the rest of the fields.
The navigation components have a binding… you should be able to add that to your exemption in your data rule.
This works … when I preview it.
When I published the layer it is still disabled … weird
May have to start this layer from scratch and re-apply the logic one at a time.
I’m curious if the navigation keyboard shortcuts (Ctrl → and Ctrl <–) still work when that control is disabled?
I’m not suggesting keyboard shortcuts as a workaround, that would be a rotten thing to do to users. I’m curious though if disabling the control might be a way to prevent normal text entry navigation from context switching and disposing work…
Just tested that, and you can still navigate with ctrl+ →
Even with the field disabled.
