RE:
If the Vendor Bank is updated on an Open Invoice, then the new Vendor Bank must be the one pulled in to the Payment Journal. Currently, even though the open invoice has been correctly updated, the payment journal ignores this and pulls in the expired Vendor Bank which no longer applies to the open invoice.It seems unlikely that there would ever be a scenario where this would be the desired system behaviour.
RE:
It refers to the estimation of potential losses that a lender or investor might incur due to the default of a borrower or counterparty over the life of a financial asset.
RE:
Power BI definitely needs a scripting language to really get work done. Any language Javascript or VBA - anything. Recorder like Excel.
RE:
This is really bad. It means every NestedJoin (which is default join from UX) messes up your column types on expansion. Every single one. Same issue when adding Index via GroupBy/ExpandTableColumn.And these errors are very hard to track down. Table.Combine can just hang spinning trying to reconcile two tables where in one a column is text and in another it's Any.So bad this is, I had to write a helper function to reapply column types based on previous types. Should be handled by the language itself.
RE:
Being able to downgrade trial SKU would be a great tool for doing a POC (proof-of-concept).
RE:
What about the "Stockkeeping Unit Exists" field on the Planning Tab? That's the one I use when I need to know if there might be any SKU impacting my planning parameters.