I’m starting to convert pages to Kinetic, so I’m new to using application studio.
I am trying to set a date on the part entry screen when the user selects Inspection Required from the inspection required dropdown.
On inspection required dropdown for the on create I’ve done this.
A couple things to try. First, in your screen shot… is there a SPACE in your Ep Binding? Hard to tell… but it looks like there’s a space after Part.
For expression, I don’t know if you need the “new Date()” portion.
Just try: '{Constant.Today}'
Not 100% sure, but that’s my first thought anyway.
Also… I don’t know if you NEED the Data Commit. I don’t know that it hurts anything. So you can leave it in there and test both ways. But if the date gets set by your row-update, it should save over once you save the record.
Did you test with and without the Data Commit? Just curious (for my own knowledge) if that is necessary or not, haha. I don’t typically add that in there, so I’m assuming it would work without.
My system has rules. The next date in a chain must be filled in before one can save as the save generates an email that shows both dates.
A BPM fires stopping the process if the dates are not filled in properly.
With classic I was able to do this by having the system estimate the second date and filling it in in a dataview. The user saved and it was all good.
Converting this to kinetic oh boy.
I finally managed to get the date to populate by hooking an event to the onblur event of the first date and calling a kinetic function. If the function sent a good result it would update the date in the dataview. So far so good.
However the BPM would fire saying the second date wasn’t populated which had me scratching my head. Its basically the same thing as the classic custiomization. I am updating the dataview. Then the user can hit save.
I remembered this thread and thought "Aha what if I put a data-commit widget after the row-update.
No error. However it did not update the data fields that were updated. The BPM did not fire.
My conclusion is that the commit somehow stopped the update process. Not sure how as the only option there is to select the data view.
So in short I have no idea what the commit widget does but it somehow stopped the BPMs from firing. They were firing before I added it and it was the only change.