Skip to main content
Version: 3.0
info

You are currently viewing documentation for CompuTec ProcessForce 3.0, which is a plugin installed and managed through CompuTec AppEngine 3.0, built on .NET 8. If you are working with older environments, you may need the documentation for CompuTec ProcessForce 2.0: https://learn.computec.one/docs/processforce/2.0/.

Please note that CompuTec ProcessForce 2.0 will be supported only until December 31, 2026. After this date, the product will no longer receive regular support or maintenance updates. Read more

CompuTec AppEngine 3.0 introduces a new architecture, and all CompuTec components, including the CompuTec ProcessForce 3.0 plugin, must be updated together to ensure full compatibility.

Before starting your installation or upgrade process, we strongly recommend reviewing the CompuTec AppEngine 3.0 and CompuTec ProcessForce 3.0 documentation.

Use Prefixes for User-Defined Fields

When adding User-Defined Fields (UDFs) to CompuTec ProcessForce objects, always use a unique prefix in the field name.

Using a consistent naming convention helps prevent conflicts with standard CompuTec ProcessForce fields during upgrades and makes customizations easier to identify and maintain.

Why use a prefix?

Using a unique prefix helps you:

  • Avoid naming conflicts with fields added in future CompuTec ProcessForce releases.
  • Make custom fields easy to identify during support and troubleshooting.
  • Simplify upgrades and maintenance.

Naming convention

Name your fields using the following format:

Prefix_FieldName

Choose a short prefix (2–3 characters) that identifies your company or customer.

Example

If your company abbreviation is AB and you want to create a field that stores weight information:

ValueExample
PrefixAB
Field nameweight
UDF nameAB_weight
Database fieldU_AB_weight

SAP Business One automatically adds the U_ prefix to all User-Defined Fields stored in the database.

Best practices

  • Use the same prefix for all custom fields created for a customer or implementation.
  • Keep the prefix short, unique, and meaningful.
  • Separate the prefix and field name with an underscore (_).
  • Do not use prefixes that could conflict with standard CompuTec ProcessForce field names.

Result

Following this naming convention helps ensure that your customizations remain compatible with future CompuTec ProcessForce updates and are easier to identify during support, maintenance, and upgrades.