Ideas for Acumatica

Feedback processing: We do not reply to all messages, but we do read them, analyze them, and work to improve Acumatica based on the feedback we receive. Ideas and comments may not appear immediately. Some legitimate ideas are flagged as spam and will be added when we review the spam folders.
Content: This portal is for product ideas and feedback only. If you need customer service assistance, contact your Acumatica Support Partner, submit a support case, or get assistance from community resources: LinkedIn Group or StackOverflow
No Reliance: Information is maintained on a best-efforts basis and may be changed without notice. Acumatica cannot guarantee the accuracy of the information provided or guarantee completion of features/ideas described on this portal.

Add SELECTOR capabilities to project attributes

When you create a new attribute , one of the control types is Selector. This lets you create a new attribute that points toward pre-existing tables. This works well in many forms, but the functionality is not present if the attribute is put into the system as a project attribute or task attribute. Would like to see this functionality added to the system.

Example: I want to create a 2nd project manager field on the projects form. I call this field Senior Project Manager. I create this as an attribute and designate the control type as selector, then choose CREmployee as the schema object. When I use this new attribute as a project attribute, it becomes a simple text field and does not let me chose from the Employee list. But if I were to use this attribute as user-defined field in the bills and adjustments form, it does function properly and let me select an employee from the list.

  • James Stange
  • Jun 9 2020
  • Attach files