PSA: Checkboxes that actually are string or integer fields in a completely different table

Kinetic ERP
, ,
1

TL;DR:

Screen Subsection Checkbox in UI Actual DB field Type
Supplier Price List Supplier Parts Primary Supplier PartPlant.VendorNum int
Buyer System Default XaSyst.SysBuyerID string
Buyer Authorized User List Default Buyer UserComp.PrimBuyerID string
Work Force Authorized User List DefaultUser UserComp.PrimSalesRepID string
Job Entry Operation > Scheduling Factors Final Operation JobAsmbl.FinalOpr int
Job Entry Operation > Scheduling Factors Auto Receive JobAsmbl.AutoRecOpr int
Engineering Workbench Operation > Scheduling Factors Final Operation PartRev.FinalOpr int
Engineering Workbench Operation > Scheduling Factors Auto Receive into Inventory PartRev.AutoRecOpr int

Also @kananga explains menu security “checkboxes” well in post #5.

Story time

image
image1041×881 34.7 KB

I was explaining to a coworker that the “default buyer” is what it says, but not at all what you assume from the screen.

When you look at this picture you think that Ca***** is the default user assigned to the REQS buyer ID.

In fact,

  1. There can be many users checked here on this buyer
  2. Conversely, each user (meaning each human, basically) can only have one buyer ID that is their default
    a. In other words, Ca***** cannot be the default on another buyer ID.

This led me to explain that this “checkbox” is not a Boolean in the database at all - it triggers a write to a STRING field on the User table. (There are actually two user tables, and it’s UserComp in this case, not UserFile - FYI.)

So I went to find the field name here on this site since it had been a while. Well apparently no one got this right (sorry).

  • This post is wrong - one asked about the “system default” and the other answered about the “default buyer.”
  • This post actually has the answer to MY question, though ironically that also was not what the OP asked - the question was about sales reps, not buyers.

And then I thought about how similar fields came up recently, so I figured it was time to document this all at once.

Anyone have any other checkboxes that are actually some other field?

2

I believe Final Operation checkbox on an operation actually sets the operation sequence number on JobAsmbl.FinalOpr (int)

Can’t remember any others off the top of my head

3

Same thing in the PartRev table for the Method. The Final Operation is stored as the numeric Op Seq.

4

Thanks @Chad_Smith and @Evan_Purdy - I updated the table and reorganized it.

I also added “Work Force,” which I think has to do with sales, as the field is UserComp.PrimSalesRepID

Funny that here it says “Default User” and I imagine that is not the idea. More like “Default Sales Rep,” right?

image
image1165×929 46.2 KB

EDIT: Oh I see what you were telling me - I had string for the ops and they are integers. I fixed them.

5

Not always a checkbox but always the same presentation mismatch - ‘Default security’ in Kinetic. In Classic, the ‘dis/allow access to all groups/users’ checkboxes.

Those values are represented by an asterisk ‘*’ in a comma delimited field, either ICE.Security.EntryList or ICE.Security.NoEntryList.

PSA #2: never use a comma or asterisk or unicode analog of either in any userID or security group ID.

2 Likes
6

Oh, right!

And then the tilde-delimited fields that @josecgomez loves on sales reps. Though that is apparently addressed in some hybrid view thing in the BAQ designer in [fill in version number here].

1 Like
7

I seem to recall this being fixed for real in 2025, but that might have been a fever dream.

8

@Chad_Smith

The aforementioned moderator wasn’t thrilled with the implementation. I don’t know if there were any changes since this post.