I am currently using Epicor Application Studio using Kinetic 2023.1.12. I have taken the fundamental and advance course and this is my first attempt at customizing the kinetic screen:
PO Entry screen, PODetail
Customization built with Application Studio
Event triggered from a Command Button
Target field: PODetail.CommentText
Goal: Update the UI only and allow the user to press Save (no auto-commit)
What I have tried:
dataview-set-current is set correctly to PODetail
Confirmed event via App Studio debug + erp-message-handler
The correct row is current at runtime
row-update parameters:
EpBinding: PODetail.CommentText
Value tested with:
“testing”
Added event-row-enable before row-update
Still no UI change, no dirty state
Added data-commit after row-update
No effect
Verified:
The field value before update
row-update fires (no exceptions)
The row remains not dirty
No errors are thrown at any step
The PO being testing is Open and I am able to edit other fields and save them.
You should really only need a row-update action after the button click trigger. If you’re already on a PODetail (Line item) record, you shouldn’t need to set the dataview or the current row… you’re already on a specific PODetail record.
I agree. But I’ve tried almost everything. The only difference, is the PODetail.CommentText has been moved into a sliding panel. The column displays the pervious values when displaying a previous open PO.