Comments
yes, correct business people want to sort by priority so the display names are very clumsy. Urgent, Normal, Low would be suitable (reversed sort order), Critical or Trivial other options. probably this might have a dependency with outlook integration of email priority... (still even in email it would not make sense to be unable to sort by priority). 1-High, 2-Normal, 3-Low. Maybe medium is more a priority than normal.Think about auto-confirmation on cases (they have the same insanely unsortable display names but here you can adopt it, however it makes no sense to have 2 different kind of 3 scale priority optionsets ;-) where we send the confirmation email and also confirm the priority with which the case has been opened (even if it is low). The reason is to give the customer the means to react if ever there is a wrong understanding and wrong priority set. labels for priority should be sensibly sortable and socially acceptable (zeroth might not be a good wording).
Microsoft added a way in C# 11 to make raw string literals by using three double-quotes, e.g.:string foo = """This is my multilinestring.""";Another option would be to use the @-sign to denote a literal string, which is also a C# construct.This would be a huge help when writing e.g. GraphQL queries in code.
I would like to add the need for functionality to adjust the price of items on multiple price lists at once. Scenario: Items (preferrably filtered bij item fields) will be adjusted with a factor on al relevant Prijce lists. And when the update on the specific pricelist is done, the former price list lines of that item should receive an ending date -1D befor the new prices are actual!