Any way to update the Part Transaction History Tracker where clause?

Kinetic ERP
1

Discovered today that parts that contain parenthesis (maybe other special characters, too, I don’t know…but suspect) will not return results in Part Transaction History Tracker, including in the Activity tab of Part/Part Tracker, despite records existing in the PartTran table.

Is there any way on a Rest call whereclause to write it in such a way that it would escape (is that the right word?) those characters to allow them to go through? I suspect as built it’s stripping away that portion of the part number, which results in no PartTran records being found because it turns it into a part that doesn’t exist.

Example clause that I’d like to try updating:

image
image383×385 6.06 KB

2

cringe GIF

I don’t have any technical advice. Just business advice that I know no one will actually take, and that’s:

DON’T USE SPECIAL CHARACTERS IN PART NUMBERS (other than dashes… dashes are ok)

3 Likes
3

What do we do when the youngin’s want Emojis on all the part numbers?

6 Likes
4

Make sure we tell 'em that the internet used to come in the mail… it’s not designed for that kinda crap!

2 Likes
5

What gets sent in the network call when this is run against a %percentpart%?

6

:laughing: I knew that I should have added the disclaimer that I’m just the guy who gets to deal with the decisions made in the past (present and near future). I’m in 100% agreement with everyone here on that front.

2 Likes
7

We know. Just giving you grief. We’ve all been there.

1 Like
8

Engineers and their “smart” part systems…

Bored Rowan Atkinson GIF by Working Title

3 Likes
9

The method that gets results for “good” parts and not for these parenthetical ones is the BO.PartTranHis.BuildPartTranHistory which sends this where clause:

PartNum = 'DFPEP-1A1-(C9582)' AND Plant = 'MfgSys' AND TranDate = '2026-03-31T00:00:00' AND StartingDate = ''


Then Response is blank, when the PartTranHist dataset should return records.

image
image267×227 3.25 KB

10

Its not the rest call that’s the issue. Its a single missing refresh call in 2025.1, they added it in 2025.2. Can fix with a simple override event in the layer in 2025.1.

This is the event you need to add:

image
image687×243 11.1 KB

4 Likes
11

Brilliant!

That fixed it. Do you know if it is the same exact event to make it work in Part Entry/Tracker activity tab?

1 Like
12

Glad it worked for you!

I did not try to fix it there as having it working in the tracker was sufficient for the time being, sorry I don’t know!

1 Like
13

No worries. Now that I know specifically what to look for I may be able to figure that one out.

1 Like