Can Rate Model Attribute be a string field instead of reference field ?

[SUBHAM_SHAW_SN]

I am willing to create a rate model separately for contractors . However, employee type field is a string instead of reference field. What are the implication if I choose a string field instead of a reference field ?

Can someone please help ?


Thanks,

Subham

[M Iftikhar]

Hi @SUBHAM_SHAW_SN,

Yes, a Rate Model attribute can technically be a string field, but it’s not ideal. If you keep Employee Type as a string, you risk data inconsistency (different spellings, case sensitivity, typos) and logic becomes harder to maintain. For instance, “Contractor” vs “contractor” would be treated as separate values. 

Using a reference (or even a choice field) gives you controlled, consistent values, and makes it easier to drive logic in workflows, resource assignments, and rate model conditions/rate lines. 

If you plan to build rate models specific to contractors, I’d recommend normalizing the field first to a choice or reference for long-term maintainability. 

Thanks & Regards, 
Muhammad Iftikhar 
 
If my response helped, please mark it as the accepted solution so others can benefit as well.