User is importing tasks that have UseRateTable checked and specify a primary resource on it as well, but there is no rate in the rate table, this causes some tasks to plan to the wrong resource or become a diamond task.
User created new parts and after the import, they plan to the wrong resource.
When importing a task that has UseRateTable checked and we specify a primary resource on it as well, but there is no rate in the rate table, this causes some tasks to plan to the wrong resource or become a diamond task.
The problem is to do with the fact that we are sending in tasks that we want to plan using the rate table, but we do not have a rate for that combination of Resource and Item, as specified on the task.
There are two ways to solve this problem:
Import the tasks without a Primary Resource - this way Orchestrate will look through all of the Resources within the Resource Group and find a resource with a rate
Enter the required entries in the Rate Table - not recommended as there is a lot more work
On import, leave the primary resource as NULL and only specify the primary resource group. Make sure the primary resource group has resources in it and that rates exist for the resources in the rate table. Also, check all the items have item production rates entered, from the Items menu, within Orchestrate.