I love a nerdy title and I love learning about cool new smart stuff.
But before you continue reading I want to say thanks to my colleagues at ForNAV, especially Michael Nielsen. Without him pushing me (again) to step out of my comfort zone this would not have been possible.
Yesterday I visited the Microsoft office in Lyngby for the first time in a very, very long time to talk about our project to split up the base app. We also talked about something else, but that will be another blog. (Soon…).
Pages: 1 2
Enums forever, but with Extensible = true property 😉
Do you have a solution for that scenario above?
Normaly i would also agree, but only as a replacement for Code- Fields with lookup to a (Code,Description- Table). Other usage may cause severe harm to your ERP- system if you are using multiple extensions (or a splitted base app)
There is a general problem with concurrent apps, accessing the same data for which we currently have no solution in BC. And if this is not solved, there will be never a stable complete solution as we and our customers expect.
In my opinion there is no possible solution for this, except doing it the old way.
But please convince me from the opposite.
Any ideas on the scenario?
BTW: I am not complaing about problems. I try to identify the key issues, that need to be solved before we can go on. And if we can’t solve them, we should stop here.
You would not design the exterieur and interieur for a real car without wheels, if you don’t know how to move the car foreward and the technical requirments for that. And if these requirements are not realizable, you would/should stop your design.
Another key issue for extended enums: How do you extend tooltips? Or will we see only the very helpfull message “Here you can enter a Type” in SalesLine.Type in the future.
A solution would have been to define default tooltips at the base (field,enum.value) but that is another thing.