Option to lower the active contracts at the Primairy contract order list
R
René de Jong
We have a configuration with 3 source systems. A primairy system on which we create de accounts and additional source system to add extra information to the primairy system. We named the source system so the primairy system is Ascending first and added "Source.DisplayName" as first field, but when one of the other system had a contract end date that is beyond the contract of the primairy system this contract becomes the active contact. And that gives problems because the base properties are not is these additional systems.
The sorting to the active contract first is in the code an can be lowered at the primairy contract order list so the "Source.DisplayName" is always first. This would solve our problem.
R
Rick van den Dijssel
Great to hear your perspective, René de Jong! I have a few more questions for you:
- Can you clarify if the primary system should always take precedence over other systems regardless of contract end dates?
- How often do you encounter issues with the current sorting method affecting your operations?
- Are there any specific scenarios where the current sorting method is beneficial and should be retained?
R
René de Jong
- The primairy source system should always take precedence. Even is the contact of the primairy system is in the future or past.
- Several time a month for all of our tenants (9x)
- No, not at our situation