Equipment Name is all numeric values

When importing from MS Excel Equipment data, if the Equipment Name is all numeric values, the import process states is must me of type string.

Workaround: In the MS Excel workbook, place an apostrophe, or “‘“, in front of the all numeric Equipment name. This will trick the software into thinking the value importing is text (or string). Do not worry, it will not place the apostrophe in-front of the Equipment Name in the Digital Wall Chart.

• Related Articles

• When exporting the data to MS Excel for Activities, Equipment, or Scope, any date values are exported in a text value

  When exporting the data to MS Excel for Activities, Equipment, or Scope, any date values are exported in a text value. This causes an issue when bulk importing the data back end, the user receives an error this is not a valid date or date is missing. ...

• Changing an SAP IAM Attribute name

  Purpose of this article - Provides guidance to end user on changing the name of SAP Attributes.  For example, possibly the end user would like to see "Outside Diameter" for "OD" on the user interface. Step 1 - Ensure you are logged into the SAP ...

• Guidelines for adding equipment within a Turnaround in DWC

  Prior to defining activities against the Equipment for the Wall Chart, the Equipment must first be added as Scope within the Turnaround. Login to Digital Wall Chart Use your SAP credentials to log in to the Digital Wall Chart application. Access the ...

• Equipment Area Null or Empty causing issues adding to Wall Chart

  The Equipment Area is not a required field when defining a piece of Equipment either via the Administrator -> Equipment App, or via the Bulk Import utility. However, when adding an Equipment to the Turnaround there is logic checking the Area to see ...

• Equipment Category Completeness graph shows any activities added after the Turnaround Start Date as “Remaining”

  The Equipment Category Completeness graph shows any activities added after the Turnaround Start Date as “Remaining”. This is a code bug. Workaround: There is no workaround for this issue. It will be corrected in the next release.