Skip to main content

Hello everyone,

Our customer wants to see the customer name and then the customer ID in the activity, currently there is the Activity ID:

 

 

Attributes have already been created:

 

We have adjusted the ActivityLabel under Parameters with the corresponding values, but no changes are displayed in PSO, instead an error message appears.

 

Does anyone have any advice?

 

Thank you!

What did you set the Activity label to? Here’s an example that works (if you have the corresponding attributes set on the Scheduling Dataset):

WOT #{Additional_Attribute.TaskSeq} - WO #{Additional_Attribute.WONo} - {Activity.#type} ({Activity.#label})

Please also keep in mind that as per the scheduling schema R&D recommends the use of additional attributes to be kept to a maximum of 4 per activity. 5 will likely be okay, but the more you add the bigger the chance of negative performance effects.


We have reduced the attributes to 3 in the cloud and have the following now:

 We have tested the ActivityLabel and the ActivityText with customer name and task number, unfortunately nothing changes in PSO:

 


You need to change ActivityLabel (not ActivityText) to see additional fields in the Gantt allocation.


Hi Alexander,

I have tried various things. Changing the ActivityLabel and the ActivityText, but the customer name and task number are not displayed in PSO:

Could it be something else?

 

Best wishes,

Anastasiya


Starting to run out of ideas… ;-) Can you check if there are different profiles etc. setup in your org for different user types?

 

And please try also with a standard activity attribute to exclude an issue with your additional attribute.


Hi @Anastasiya Dzembak 

ActivityText controls what is displayed in the Gantt chart and ActivityLabel is used everywhere else. Try setting ActivityText to {Activity.Customer}. You cannot specify {Customer.name} or {Customer.ID} at the moment. This would be a new feature request.


Hi @Aloka Munasinghe 

I have just tried this and unfortunately it does not work.   

In our test environment it works, the system takes the customer name and the task ID:

 

 

Is there another possibility?

Thank you!


Reply