Unable to create 2nd attribute in one rate model in PPM module

VIKAS MISHRA
Tera Contributor

I have created one attribute for location.

Second attributes needs to be created on the bases of Group. 

Basically rate model first check the group attribute and then check the location. 

However i have created one attribute for location one but when creating the second one i am getting error "Rate lines exists for this rate model."

I have checked the documents as per that we can create max 10 attribute, but here i am not even able to create 2nd.

Please suggest.

 

VIKASMISHRA_0-1736937462422.png

 

1 ACCEPTED SOLUTION

PaulaaO
Mega Sage

Hiya, I just tested on my end and I get the same message if the Rate model has rate lines attached to it which makes sense, cause the rate lines get created based on the current rate model which if you tweak it, it creates inconsistencies.

 

From the looks of it you have 2 options:

- if you wish to use the exact same rate model (especially if it's already attached to a demand/project), you need to remove the rate lines, add the attribute and then re-create the rate lines

- create a brand new rate model from scratch with the desired attributes and then create the rate lines

 

Hope this helps 🙂

View solution in original post

2 REPLIES 2

PaulaaO
Mega Sage

Hiya, I just tested on my end and I get the same message if the Rate model has rate lines attached to it which makes sense, cause the rate lines get created based on the current rate model which if you tweak it, it creates inconsistencies.

 

From the looks of it you have 2 options:

- if you wish to use the exact same rate model (especially if it's already attached to a demand/project), you need to remove the rate lines, add the attribute and then re-create the rate lines

- create a brand new rate model from scratch with the desired attributes and then create the rate lines

 

Hope this helps 🙂

Hi Paulaa0, what you said is correct and it worked. 

However need one more help. 

I want to create 2 attribute , first priority attribute is to check if user is part of a particular group , if he is then the next attribute which runs on the bases of location that will not work and only based of 1st attribute it will simply allow to provide the cost. 

And if user is not the member of that group then it should check the second priority attribute and on the bases of location the cost should be assigned.