Frequently Asked Questions - Custom Fields on Standard UIs
(Plex Community Post dated November 23,2023 )
Why did Plex develop custom fields? What are some examples use cases?
Every business is unique. That's why we introduced custom fields as part of our Plex Extend initiative. It's all about giving you the power to tailor your Plex experience to match your specific needs and capture the data most important to you, whether you're in a specialized industry, have unique internal processes, or simply want things your way.
Some creative uses for the first release of custom fields include:
- Classifying reasons for late supplier deliveries per release
- Crafting customized work orders to capture advanced maintenance processes
- Swiftly responding to supply issues with alternative OSP and mill part data
- Adding extra dimensions to containers of raw materials
- Capturing automotive-specific details like VIN or vehicle vocation on RMAs
- Organizing journal entry types and date spans more effectively
And this is just the beginning! Once custom fields are integrated with APIs and VisionPlex reporting, the possibilities are practically limitless.
Are custom fields included with my existing subscription? How do I get started?
Custom Fields are available to all Plex UX customers starting November 27, 2023. Plex Champions can add new fields to over 35 standard objects (like orders, containers, and parts). We've set a reasonable limit of 25 custom fields per standard object per PCN. If you haven't made the transition from Classic to UX yet, Custom Fields will be automatically available when you do.
To get started, simply follow the Custom Fields article on the Plex documentation site.
What's the end user's experience, and can I control where the fields appear?
When you enable a custom field for an application, it seamlessly integrates within a 'Custom Data' section for all users with access to that screen. No pop-ups or side panels, just a smooth, intuitive experience.
Custom Fields adapt to their surroundings. They can be edited on forms (like Part Detail) or editable grids (such as GL Journal Detail) but appear as read-only on report-like grids (like Parts or Inventory). You have control over how they're sorted within each Custom Data section.
What standard objects and applications are supported currently? Will these expand?
In this initial release, we support over 35 standard objects (like orders, containers, and parts) and more than 110 Plex-authored screens. Explore all supported standard objects and screens in the 'Standard Object Actions' report under the 'Data Extensions' menu in Plex UX. This report always presents the latest supported objects and screens.
And guess what? We're not stopping here! Each product manager is committed to expanding custom field support across more standard objects and screens over time according to need. If you have a particular object or screen in mind, share your needs with us via an Exchange suggestion. Be sure to explain why it’s valuable to you and what outcome you’re trying to achieve!
How does security work for custom field management and usage?
Setting up security for custom fields is simple. Plex Champions only need access to add or update custom field definitions and link them to screens. No additional security access is required for end-users. If a user can see or update standard data on a screen, they’ll automatically have the same access for custom fields.
How do I make a field required? What validations can I add to fields?
You can make any field required, except for Booleans (true/false values). The 'Required' option becomes available based on the field type you select in the custom field definition. Each field type offers different validation options. Numbers can have min/max ranges, text fields can be set to a maximum length, and more. For the nitty-gritty,
What is the difference between ‘Name’ and ‘Label’? Can I change them later?
In a custom field's definition, you’re prompted for both Name and Label:
- Name: A permanent identifier for technical purposes, not visible on most UIs. Name must be unique per standard object and cannot change once created. It is important to use the same name for related fields across PCNs, especially if you plan to use them in future enterprise integrations (APIs) or reporting.
- Label: The text users see to caption the field on forms and grids. You can freely change labels over time, and they do not need to match across PCNs.
Can I create ‘Dropdown’ or ‘Picker’ fields? How do Allowed Values work?
Absolutely! While you can't link fields to data sources or setup tables, you can create fields that display as fixed-list dropdowns or pickers (depending on the number of selection items) by specifying Allowed Values on Text fields. Learn more in our official documentation.
Can I have different custom fields per PCN?
Custom fields are defined per PCN, allowing you to have unique sets of fields for different PCNs. This flexibility comes in handy when managing plants in distinct industries. If you create the same custom field in multiple PCNs, remember to give them the same Name (even if the Labels are different) for future capabilities related to APIs, VisionPlex, and enterprise field management.
When and how will Custom Field APIs be available? Can they be used alongside data sources?
Exciting news on the API front! We're developing a standalone Custom Field API within the Open API framework (developers.plex.com). It's scheduled for a beta release in Q1 of 2024. This API will empower you to retrieve, search, and update custom field data on all supported records. And here's the great part – it's compatible with both Resource IDs and Keys, making it versatile enough to work with Open/REST APIs and traditional data sources. While we're also planning to integrate custom fields more seamlessly into existing APIs in the future, this standalone Custom Field API is our fast-track to provide API support across the board, maximizing value for our customers.
How will customer-authored reporting work for custom fields? Why aren’t custom fields available in SQL (SDE / ODBC)?
The SQL development environment offers querying access to numerous standard data tables. Data extensions such as custom fields are not near-term candidates for the current SQL environment because they are tenant-specific and stored in an alternative schema.
But fear not! We are enhancing VisionPlex to support custom fields natively by linking them to your SQL data sources. This means you'll have the freedom to use custom fields seamlessly in your VisionPlex reports. You can display, group, sort, conditionally format, use in expression/calculations, and perform all the actions you'd expect, just like with standard fields available in VisionPlex today. We're planning to release this capability to our participating Limited Availability customers in Q1 of 2024.
Furthermore, getting your custom field data into your data warehouses is on our radar. While data extensions won't be available in ODBC, you'll have access to our Custom Field API, which you can use to extract custom data into your data warehouses.
What about other / future capabilities? How can I stay plugged in?
After we finish rolling out searching, API, and VisionPlex reporting support for custom fields, we're gearing up for even more exciting features. Our priority is to support custom fields on printed documents, like BOL (Bill of Lading). In the grand scheme of things, we're looking at supporting workflow tokens, IntelliPlex reporting, enterprise field management, and more.
Want to have a say in shaping Plex's future? Join our Plex Extend PAG (product advisory group)! We're on the lookout for enthusiastic customers willing to engage with our limited availability programs, coming throughout 2024, not just for Custom Fields but for other exciting Plex Extend capabilities too.