Screenshot Example

Issue

This error message means that the Build Plan Number, or "BP#" for the new BP is longer than 41 characters (including spaces). This error can occur in companies which use FCX - QB sync because the QB "Customer Job" field has a 41 character limit and the FCX BP# syncs to this field. The solution depends on how the BP# is generated during GBP:

• IF the BP# was Custom entered: The user must simply reformulate their desired BP# to be 41 symbols or less.
• IF the BP# was autogenerated based numbering convention: Some contributing Requisite value is too long and must be shortened to bring the BP# total generated length to 41 characters or less.

For more information on the BP Numbering Convention see: What is the BP Numbering Convention?

How to Troubleshoot

First, you must determine what the BP Numbering Convention is and thereby, what its contributing Requisites are. There are multiple ways to do this:

• Administrators and PLMs can directly access this info as described below.
• Contact your PLM and request this info.
• Unless it has been changed since implementation, your company's configuration for this and many other parts of the system is documented on your FieldCLIX Implementation Project website.
  • The relevant page URL should be: https://sites.google.com/view/YOURCO-fcx-imp-project-pg/configuration-documentation/reference-number-formats/bp-numbering-convention
  • Replace "YOURCO" with the name of your company as entered in FCX, IE, "Wireless."
• You can extrapolate the formulation by looking at a generated BP's number in your system.
• If all else fails, submit a ticket to support.fieldclix.com. You can also use the FCX SUPPORT Widget imbedded in the lower right corner of the FCX Wiki.

Upon investigation, you will probably find something like this:

NOTE, Individual Requisite Value character limits applicable to numbering conventions are usually enacted through Policy because FCX fields do not generally have customizable character limits.

Now that you know the Requisites that contribute to your BP Numbering Convention, you can check the source of each one to ensure they are not longer than the Requisite Value character limits imposed by policy. Here's an example of how to check for a BP Numbering convention like that above:

Solution

When you find the offending Requisite Value, simply change it to comply with the character limit policy.

CAUTION You should consult your PLM before changing Abbr or Code Values on cards because this change will not directly affect some preexisting records which feature that Abbr or Code and additional steps are required if you want to updated the Value everywhere in the system.