Extended Part Data Token - XPARTDATA (Overview and Reference)

Extended Part Data Token - XPARTDATA (Overview & Reference)

Some Microvellum users have expressed the need for a way to add custom part data to their reports. The limitation lies in the database fields that are available for this purpose in the database.

As of the 15.6 release, there is a new token available that populates the database with custom data for that part. Once the data is in the database, you may then add to your reports. You will add this token to each part for which you need that data.

All token parameters work the same and have the same format.  They require two pieces of information with an optional third piece.  Separate all segments of the data with a pipe symbol delimiter in the format:  Field Name|Field Value|Spreadsheet Comment  (e.g. "XD04|13.4|Part Weight"). The Field Name and Field Value data are required; the Spreadsheet Comment data is optional.


           XD04|13.4|Part Weight


Generic fields available:

  • XD01
  • XD02
  • XD03
  • XD04
  • XD05
  • XD06
  • XD07
  • XD08
  • XD09
  • XD10
  • XD11
  • XD12
  • XD13
  • XD14
  • XD15
  • XD16
  • XD17
  • XD18

Predetermined 'system' fields available:

  • UDID (User Defined ID)
  • LOCATION1
  • LOCATION2
  • FINISHPRIORITY
  • EDGESEQUENCE
  • IRREGULARSHAPE
  • OVERPRODUCTIONQUANTITY
  • UNDERPRODUCTIONQUANTITY
  • LABELPOSITON (See section on this)

The final nine names are predefined fields in the database – also known as "system" fields. That means instead of entering a comment as described above to help remember the purpose of one of the generic fields (XD01 – XD18), you would use one of these six system fields. This would be true, particularly if you require data that matches one of these system field names.

You must work with the tokens in the spreadsheet. They are not currently accessible from the Part Properties interface.

The parameters for this token support formulas. For example, if you want to reference the value for the width prompt in database field XD02, enter the following text string exactly:  ="XD02|"&L!Width


These are the fields as populated to the work order database.


Use the values shown above in reports and labels as needed.

Auto Nest Labels - LABELPOSITON

Use the LABELPOSITION data field to place your auto nest labels in pre-selected positions on your parts.

The LABELPOSITION XPARTDATA works the same as all the XPARTADTA Fields. They require two parameters with an optional third. Each segment of the data must be separated by a pipe symbol delimiter in the format:

<field name>|<field value>|<spreadsheet comment> (e.g. “LABELPOSITION|5;10;0|Part Label”).

The Field Name and Field Value data are required; the Spreadsheet Comment data is optional.

    LABELPOSITION | 5;10;0 | Part Label

Label rotation is based on the capabilities of your machine. Most machines only allow a simple rotation of the labeler head.

The X & Y Location of an auto-label is based on the Machine Point of the individual parts.


Fig. 5 – Part Drawn in 2D



Fig. 6 – XPARTDATA in Spreadsheet



Fig. 7 - LabelPosition XPARTDATA Column in the Processing Center and Resulting Label Placement in the Composite DWG



    • Related Articles

    • Overview & Reference: 3D Draw Token and 2D Elevation Token

      Microvellum's library data contains two drawing token columns that serve a range of functions depending on the specific token used in that column. This article will provide an overview of the function of those two columns and the three accompanying ...
    • Hardware from Machine Tokens (Overview)

      Microvellum software can now accumulate and populate hardware to the work order database based on specific machine tokens. It is one of the useful new Microvellum features supported in build 15.6.2201 or greater. This new ability works only with the ...
    • Microvellum Flatshot Token (Overview)

      As of release 15.6, the speed of processing when using the Microvellum Flatshot token has been significantly increased for some types of products. More importantly, the token can also display hardware as part of the Microvellum Flatshot token. This ...
    • Microvellum Flatshot Token (Reference)

      The purpose of this article is to document the parameters of the Microvellum Flatshot Tokens available as of build 15.6. Elsewhere in the Microvellum Knowledge Base, you will find articles and tutorials giving an overview of the token, how to access ...
    • Microvellum Data Dictionary

      Microvellum Data Dictionary Introduction This manual is a guide to the Microvellum Factory and Work Order Databases. This manual has four sections. The first section includes this introduction, and the remainder is General Information about this ...
    • Recent Articles

    • The Range Hood - Add-on

      About the Library Add-on This is a “Master” Range Hood product capable of being used as is or saved back to the library numerous times in unlimited number of different combinations.  This Library Add-on is compatible with the Foundation Library. This ...
    • Toolbox Release Notes | Build 22.1.0406.641

      The following Release Notes apply to Toolbox Build 22.1.0406.641 Database Management Resolutions: Resolved an issue that caused template level projects to be deleted when deleting a seemingly “empty” category (this was caused by a mix-up in the ...
    • Microvellum Foundation Library Release Notes | Build 22.0407

      The following release notes apply to Microvellum Foundation Library, Build 22.0407 Please make sure you are selecting the correct specification group when drawing products. There may be specification groups for both metric and imperial. Additions: ...
    • Toolbox Release Notes | Build 22.1.0325.641

      The following Release Notes apply to Toolbox Build 22.1.0325.641 Toolfile Resolutions: Resolved an issue in certain post names where the pecking number was not working. Resolved an issue in certain post names where some face 6 machining was falling ...
    • Toolbox Release Notes | Build 22.1.0317.641

      The following Release Notes apply to Toolbox Build 22.1.0317.641 Database Resolutions: Resolved an issue where the user experience took longer than necessary to start.   Materials Resolutions: Resolved an issue where with formulated materials the ...