Parse a Type Code

Parse a Type Code

Once you have a published rule (see Type Code Rules), parsing is the easy part. You paste a code, the app decodes it, and you turn the result into a product or download it as an AAS.

Open Type Code → Parse Code in the left menu.

You need a published rule that matches the code first. Parsing looks through your published rules for one whose pattern fits; a draft or retired rule is never used.

---

Parsing a code

What you are doing: decoding one code and seeing what it contains.

How: type or paste the code into the Type Code box and click Parse (or press Enter).

Example: paste NW-4021-P075-U3 and click Parse.

---

Reading the result

When a rule matches, a green Parsed successfully banner shows the rule name and version that was used, followed by:

• Summary cards: Product Family, Manufacturer, the Raw Code, and how many tokens were found.
• Extracted Tokens table, one row per segment:

Column	What it shows
Token	The segment's name, e.g. Power.
Extracted	The raw text pulled from the code, e.g. P075.
Interpreted	The decoded value, e.g. 7.5 kW. If it is the same as the extracted text, it is shown plainly.
Status	Valid or Invalid.

If any token is invalid, a Token Validation Errors panel expands to say why.

For our example you would see Power extracted as P075 interpreted as 7.5 kW, and Voltage extracted as U3 interpreted as 400 V.

If no rule matches, you get a red No matching rule found message with the reasons, and a Try Again button. This usually means the rule for that family is not published, or the code has a typo.

---

What to do next

Three buttons sit under a successful parse.

Button	What it does
Create Product from This Code	Creates a new product (a variant) from the decoded values, filled in with everything the rule maps, plus the shared data from the rule's base product.
Download AAS	Downloads this decoded code as an AASX package, JSON, or XML, without creating a product. Use it for a quick one-off export.
Parse Another	Clears the result so you can paste the next code.

Create Product is the usual choice: it adds the variant to your catalog so you can manage and publish it like any other product.

---

After creating a product

A code cannot supply every required value, so a product created this way may be missing some required technical-data fields. The app does not force you to fill them at parse time, so:

1. Open the new product from the Product Catalog.
2. Go to its Technical Data tab and fill in anything still required (see Technical Data).

Do this before you rely on the product's export.

---

Hints

• Parse one code first to check the result looks right before you create anything.
• If nothing matches, check the rule for that family is published, not still a draft.
• The rule name on the banner tells you which rule decoded the code. If it is the wrong one, your rules may overlap; narrow their scope.
• Use Download AAS for a throwaway file, and Create Product when you want to keep and manage the variant.

---

Limitations to know

• Only published rules parse. A draft or retired rule is ignored.
• A parsed product can be incomplete until you fill its required technical-data fields by hand.
• A code must match exactly one rule. If two published rules could match, the app refuses rather than guess, so keep rule scopes distinct.

For technical users

Parsing runs the code against published rules only, selecting by scope prefix then regex match, and fails loudly if more than one matches. The result is a dry run and is not persisted until you act on it. Create Product dispatches CreateProductFromTypeCode, which keys the new ProductType by order code, copies base-product data, and saves technical data with SkipRequiredValidation, which is why required fields can be absent afterwards. Download AAS builds the environment on the fly (AASX, JSON or XML) without creating a product.