App Studio, Events, Row-Find - Working example,

Posting this because of a long battle with getting Row-Find to work,
hoping some others may find it helpful.
(there are a couple of other posts related to this issue)

I always got an “Errors in criteria parser” error because could not get the syntax quite right, or I’d get the syntax to the point where there were no errors, but the incorrect value was returned.

Example, I needed to find a specific row in OrderDtl given a previously saved OrderLine number and then make that the current row using row-current-set

image

Note: row-find has 3 modes, RowIndex, Exists, or Count
this example uses RowIndex

Note: RowIndex is a zero based index of the existing rows (i.e Not the OrderLine number), which is what row-current-set needs in the next step

Here is how the row-find is setup:

image

TransView.OrderLineNum is set earlier in the event using row-update to save the current line.

I tried lots of variations on the expression syntax, what I hadn’t tried though was using a single ‘=’ sign…to me this is very odd…expressions typically use “==” or “===” and "=’ is typically reserved for assignment…(I thought)

The EpBinding TransView.OrderLineRowNum is the RowIndex for the line I am looking for in the OrderDtl view (or -1 if not found).

This is how the row-current-set is setup:

image

Quite simple once it works…

Oh, and btw, dataview-condition widget follows the same concept

6 Likes

I haven’t looked at it, but since you say it’s a working example, thank you. :heart:

Scott,

Thank you for posting this. The syntax of row-find and row-current-set has been driving me nuts! This could all be solved by… some formal documentation from Epicor. :disappointed:

4 Likes

At least for 2024.1, there is quite a bit of formal documentation for Application Studio:

Application Studio Fundamentals User Guide - 214 pages

Kinetic Application Studio Reference User Guide - 457 pages

Kinetic Application Studio Extensions User Guide - 143 pages

2 Likes

yes, but as an example in application studio reference for event actions/triggers they lightly cover 22 ‘most commonly used’ out of about 70

1 Like

If there are improvements wanted in the documentation, we need to help Epicor prioritize those needs. Send comments to documentation@epicor.com. @karihagedorn also watches this forum, so mention the less-frequently used events that are important to you to help them fill the gaps. Others can chime in to push certain items over others.

***Edit: Per Kari below, use Epicor Ideas!

1 Like

Please submit any documentation requests via Epicor Ideas, by using the Education Material Category for the specific product. If you are submitting requests directly to me or our documentation email address, other customers do not have the ability to vote and increase priority.

5 Likes