Without his guidance, I would have struggled for a lot longer berfore getting here.
THANK YOU!!!
After I added the condition and also the second trigger of ‘orderDtlRowChanged’, it seems to be working like a champ!
I would say for my situation, the correct answers were:
Post #6 - Create the REST like this in separate event.
Post #9 - This is the trigger for line row changes. Use condition from Post # 13. Hook condition to event-next going back to your REST event you set up in Post #6.
Post #13 - This is the trigger for first loading. Hook condition to event-next going back to your REST event you set up in Post #6.
Post #14 - This told you to use 2 separate triggers to cover loading and line changes.
I ran into the same problem, how I worked it out was to make a really simple one in classic then uplift it with the conversion tool. I then took a look at how it was made. Sorry I am a bit under the pump at the moment, and have been meaning to do a write up if only to go into my archive.
I don’t know if I should be embarrassed by this or not, but I’ve never seen reference to FKV before. But, I entered Epicor in Kinetic forms and only played in Classic a little during initial implementation sessions as a stop gap while Kinetic forms were still being built and released (it was a painful time!).
I guess I’d have to agree that FKV doesn’t exist in Kinetic… could be wrong, but I’ve never come across it??
To me, this sounds like a straight forward rest-kinetic event to populate your Part dataview.
You have a Part dataview set up, tied to the Part table and dataset… so you just need an event to populate it:
There’s already a stock event for ColumnChanged_OrderDtlPartNum
I guess I would first attempt to tie my custom event after that one.
Trigger:
event
after
ColumnChanged_OrderDtlPartNum
Add a Rest-Kinetic action (below is an example I have from a custom dashboard, but the settings should be the same):
As long as the trigger (timing of the event) works… This should use the OrderDtl.PartNum as the parameter in your GetByID rest call. It should pull the full Part dataset into your Part dataview. Then you just bind your control (textbox or whatever) to Part.MPD_Description02_c and it should display.
If you switch to a different OrderDtl record (row), it should perform another rest call and bring back that part’s corresponding part dataset.
I set mine up like my example above and it worked.
I do NOT have a parent/child relationship set up in my dataview, but that may not be an issue either way.
I guess if you want to post up picks of your rest settings and more detail on the result, we can dig in. Can you expand the drop downs? Might have some clue in there.
Preview and Response will probably be empty since it failed… but do you see anything in the Payload (is your rest call sending what it should be sending)?
Without his guidance, I would have struggled for a lot longer berfore getting here.
THANK YOU!!!
After I added the condition and also the second trigger of ‘orderDtlRowChanged’, it seems to be working like a champ!
I would say for my situation, the correct answers were:
Post #6 - Create the REST like this in separate event.
Post #9 - This is the trigger for line row changes. Use condition from Post # 13. Hook condition to event-next going back to your REST event you set up in Post #6.
Post #13 - This is the trigger for first loading. Hook condition to event-next going back to your REST event you set up in Post #6.
Post #14 - This told you to use 2 separate triggers to cover loading and line changes.
I honestly don’t know which is better. As convention, people use it as a social credit / means of ‘rewarding’ the person who provided the solution and so it is seen as rude to ‘steal’ it for yourself. I believe a solution is worth a lot of points on the leader board.
However, all that is pointless internet points. As far as a functional purpose, it makes is easy to see if you are searching on a problem, if the search result was ever solved, and it makes it easy for people scanning the forums for people who still need help. It also puts the post marked as solution at the top with the original problem statement, saving people time. In that case, a post that has the full and complete solution would be ideal, but often times the solution is spread out over a series of posts, and sometimes even over multiple users. In that situation some people just pick the person who had the greatest contribution or the last post that was part of the solution.
And some people make a summary and then mark it as the solution, ‘rewarding’ themselves.
