back to top

How-to: Creating a New Manager Field in Infor CRM

There may be many routes to the same solution, but here is one method to get a new Manager field into Infor CRM. First and foremost, do this on a test system. Also, backup your database prior to making any changes.

In this scenario we want to create a new Support Manager field on the Ticket Entity level.  To begin, I will create a new ID field in the Ticket table. This is done in the Administrator program.

1. Open the Administrator.

 

 

 

 

 

 

 

 

2. Go to Manage/Database.

3. Go to the Ticket table.

4. Right click on the Ticket Table and choose Create New Field.

 

 

 

 

 

 

 

5. I have named the new field “SupportManagerID”.  In the Display Name I have removed ID and named the field “Support Manager”. The field name cannot contain spaces, but that is allowed in the display name.

 

 

 

 

 

 

 

 

 

 

 

6. Once your field is created, click on OK and click on the Red Check mark on the icon bar. This will apply your changes to the database.

 

 


Now, we will switch programs and open the Application Architect.

1. In the Application Architect go to View/Project Explorer.

 

 

 

 

 

 

 

 

 

2. Expand your Entity Model under the VFS.

 

 

 

 

 

 

 

 

 

3. Right click on the Ticket table and choose Update Properties.

 

 

 

 

 

4. Choose Update Properties and scroll to the bottom of the list of Properties.  You will see the new SupportManagerId field, check the box and click on Finish.

 

 

 

 

 

 

 

 

 

 

 

5. Now that you have checked that box, you have included it in the Entity. If you want that field to be available to use on a form, you must first Build the System.

6. Hold down the Ctrl key on your keyboard and click on the “Build Web Platform” button.

 

 

 

 

7. You can open your Output window to view the progress. View/Output Window.

8. The system will tell you when the Build is complete.

 

 

 

 

9. If you want the Username to show up correctly on your form, you need to create a relationship in the Entity before you add the field to the Ticket Details form. If you don’t then it will show a User ID, and you will not be able to determine the correct user.

10. Create a relationship to your new SupportManagerID field. Go to the Ticket Entity on the left side of the screen and highlight Child Properties. Right click on Child Properties and choose “New Relationship”.

 

 

 

 

 

11. Set up the new relationship as in the graphic below.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

12. Connect your Support Manager field to your User ID in the User Table.

13. Click on OK when finished. Make sure you change the Property Name and the Display Name to Support Manger.

14. If you are bundling your changes for another system make sure you add this relationship to your bundle. If you are doing this on your LIVE system, you can skip this step.

15. Make sure you save everything and then Build/Deploy the database. Click Save All.

Now you can add your field to a form.

1. Find the Ticket Details form in the Project Explorer and double click on it.

 

 

 

 

 

 

 

 

 

 

 

2. This will open your form in the main part of the screen.

 

 

 

 

 

 

 

3. Create a new field with a username as the field value. I am going to right click on the form where I want my new field and choose Insert/Lookup/User.

 

 

 

 

 

 

 

 

4. Now I will adjust the properties of this field to work with our new SupportManagerId field. We will be using the relationship that we just created called SupportManager.

5. Go to View/Properties, which will open the Properties window.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

6. Make sure your new field is highlighted so you access the correct properties.

 

 

 

 

 

 

7. Change the Caption Property to “Support Manager”.

8. In the Data Bindings field, choose your SupportManager field. Double click on it to move it to the Binding field on the right side of the screen. This is your new relationship field, not the ID field. Click on OK, when finished.

 

 

 

 

 

 

 

 

 

 

 

9. You can save your form and Build/Deploy your system.

10. When you are finished, you can look in the Web Client to see your new field.

11. Make sure you can add a user to the field and save the record. Switch to another record and return to the original record to make sure your data is bound to the record.

That’s it!  Notice the Support Manager field on the bottom right of the screen.

 

 

 

 

 

 

 

Contact Customer FX for your CRM project
We let our expertise speak for itself - let us know how our all-star team can help on your CRM project
About the Author
Dale Richter
Dale Richter
Director of Training- I have worked with Customer FX since 1997

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Infor CRM SLX 10.0: Delegate Ownership Changes for “Everyone” Records

Learn how the new EveryoneOwnerAssignment secured action in Infor CRM SLX 10.0 allows designated users to change ownership of Everyone-owned records without requiring Administrator access.

Related Articles

Infor CRM Sync for Exchange: Action Required by August 31, 2026

Using Infor CRM Sync for Exchange with Microsoft 365? Your Exchange administrator must update tenant settings by August 31, 2026 to prevent sync disruption.

[Webinar] What’s Coming Next for Infor CRM SLX and Why v10 Matters

See what’s coming next for Infor CRM SLX, including new marketing workflows, automation improvements, and reasons to consider upgrading to v10.

Disable Caching in Infor CRM SLX Web Client

In the rare case caching is causing issues in the Infor CRM SLX web client, it is possible to disable specific types of caching by making edits using Application Architect, and then deploying.

Exploring AI Options for Infor CRM v10

I've started taking a closer look at the AI capabilities built into Infor CRM v10. Over the next several posts, I'll share what I learn. From the built-in features and supported AI providers to implementation considerations, costs, and practical use cases.

Related Videos