+5Hi,
I am looking to see if I can get a better idea of what values are expected to be passed against ‘StdNameId’ attribute when working with the Part Handling API please - (ifs.cloud/main/ifsapplications/projection/v1/PartHandling.svc).
I believe that it requires a numerical value from 0 to 10, but I want to understand what outcomes are driven by each of these values please. Is there documentation that supports the API usage here other than the API Explorer?
Thanks
Best answer by Piyal Perera
Hi
Sharing my findings from a Cursor-assisted technical/functional search. I hope these insights are beneficial.
StdNameId on PartHandling.svc is not a fixed 0–10 enum. It is a foreign key to your tenant’s Part Standard Names master data. The “10” you may have seen is the numeric field size (up to 10 digits), not a list of allowed codes.
In the Part Handling projection, StdNameId is defined as a numeric reference to the Standard Names registry:
It links to StandardNames via StandardNameIdRef
Each ID maps to a user-defined standard name text (for example “COMPUTER”, “FUSE”, “BEARING, CYLINDRICAL ROLLER”), plus optional per-language translations. There is no built-in meaning where ID 1 always means X and ID 2 always means Y — the meaning comes from your environment’s Standard Names setup.
When you create a part without supplying StdNameId, the server defaults it to 0, meaning no real standard name assigned:
New standard names get sequence-generated IDs (STD_NAME_SEQ), not a fixed 0–10 range.
regards,
Piyal
+12Hi
Sharing my findings from a Cursor-assisted technical/functional search. I hope these insights are beneficial.
StdNameId on PartHandling.svc is not a fixed 0–10 enum. It is a foreign key to your tenant’s Part Standard Names master data. The “10” you may have seen is the numeric field size (up to 10 digits), not a list of allowed codes.
In the Part Handling projection, StdNameId is defined as a numeric reference to the Standard Names registry:
It links to StandardNames via StandardNameIdRef
Each ID maps to a user-defined standard name text (for example “COMPUTER”, “FUSE”, “BEARING, CYLINDRICAL ROLLER”), plus optional per-language translations. There is no built-in meaning where ID 1 always means X and ID 2 always means Y — the meaning comes from your environment’s Standard Names setup.
When you create a part without supplying StdNameId, the server defaults it to 0, meaning no real standard name assigned:
New standard names get sequence-generated IDs (STD_NAME_SEQ), not a fixed 0–10 range.
regards,
Piyal
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.