on
RE:
Would definitely be useful to be able to share segments as my team would use the ones I already have set up. Also very handy to have the date set when creating a journey.
RE:
Would provide great value to users!
RE:
I would like to emphasize that the solution we need will greatly contribute to our accounting department working much more efficiently in the system. Our current solution is very manual and time-consuming. Implementing this fix will significantly improve our workflow and productivity. Please let me know if there is any additional information I can provide. I hope you put pressure on this case so the fix will be given priority and resolved in a timely manner.
RE:
As we have many vendors who constantly change their bank accounts this would be beneficial to Uniting account payments
RE:
Hi BC Team,I wish expected this is on your roadma in 2024 or 2025
RE:
tes comment
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.