+19Hello,
We have a new Foreman attribute that should allow the user to Select from the Employee List when adding new projects. We set up the attribute as follows:
When we try to add Foreman to Project Attributes screen, it’s not in the list. Why? What have I missed? The attribute appears to be active and is not used elsewhere. Thank you!
Best answer by Nayan Mansinha
I checked with the CRM team and found out that selector attributes were specifically implemented for UDF functionality and was never added to Attributes. And UDFs will replace Attributes at some point in future.
+19Hi
Please find the code below for reference.
+19Thank you Naveen,
I checked other screens where attributes can be attached, like customer class/vendor class. I could not connect our new Foreman attribute to any profile screens that I checked. I AM able to see the new attribute in document screens like AP Bill. Can this be changed? It will be ever-so-useful if I can use the Selector-type attributes everywhere attributes can be used. Thank you.
Laura
+1hi
I have verified this and experiences the same issue as you indicated, where attribute that is marked as selector doesn’t show in attribute configuration. We couldn’t find the root cause of it.
However, I was able to configure the selector using “User Defined Field” feature of Acumatica that provide user ability for user to create few field as required without coding. Can you review whether this helps for your need.
Please review this video for creating the user defined fields with out coding -
+19Thank you for your response and for the work-around. I did notice I could add the Attribute as a User-Defined field on documents and batches, but did not realize Some Attributes can only be User Defined Fields while other Attributes can be Attributes. I read the help and found no descriptions of why one kind of attribute is set up in Attribute screen but cannot be used as an Attribute.
I would like to see all Attributes be Attributes, instead of needing two ways to set up attribute fields and two places for users to enter attribute data on the same project. I will enter this as a Product Idea.
Thank you, again.
+19Hi,
Hi
+2I checked with the CRM team and found out that selector attributes were specifically implemented for UDF functionality and was never added to Attributes. And UDFs will replace Attributes at some point in future.
It is good to know the reasoning for the Selector only being for UDFs, however I was a little confused that Attributes will be replaced by UDFs in the future. Aren’t attributes linked to Classes to extend extra field for specific groups, whereas UDFs are more Document level?
I checked with the CRM team and found out that selector attributes were specifically implemented for UDF functionality and was never added to Attributes. And UDFs will replace Attributes at some point in future.
Something that it’s cool with Attribute is that I can add it to only one class of “service order” , and put it Required for this specific type, and not all the type. If I go with UDF, no possibility to put “Required” or set which class to put this UDF. I’m I right?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
