on
RE:
Would help a lot.
RE:
Please add as will be very beneficial.
RE:
Yes, I support it. This possibility is needed.
RE:
Without the ability to carry these formats all the way into Excel from PBI semantic models users will just go around the model and create their own versions, defeating the object of the whole exercise. Please let's get this upvoted and done.
RE:
test
RE:
Why isn’t this available? This would be great to have.
RE:
Thanks Shravan. It is great that finally we are getting basic functionality restored, but it only allows 5 pre-defined columns that are very basic. Is there anything in the roadmap to allow users to define the columns (or attributes) to be exported?
RE:
A base single Instance CU would be work well. No need to recreate with extensions.The SI CU just needs to store KeyValue pairs to be used later in a process. Keep it simple.codeunit 55108 SingleInstanceKeyValues{ SingleInstance = true; var KeyValues: Dictionary of [Text, Text]; procedure SetKeyValue(KeyName: Text; KeyValue: Text) begin if KeyValues.ContainsKey(KeyName) then KeyValues.Remove(KeyName); KeyValues.Add(KeyName, KeyValue); end; procedure GetKeyValue(KeyName: Text) KeyValue: Text begin if KeyValues.ContainsKey(KeyName) then exit(KeyValues.Get(KeyName)) else exit(''); end; procedure RemoveKeyValue(KeyName: Text) begin if KeyValues.ContainsKey(KeyName) then KeyValues.Remove(KeyName); end;}
RE:
This function is very important to the TSC team as PO/SO are attached daily. We also view attachment on a daily basis for research purposes when processing customers payments.
RE:
Great observation, Hylke! It is a must implement idea! Small details like currency abbreviations can have a big impact on user experience, especially in a global context. It’s impressive how such tweaks can enhance clarity and usability.