on
RE:
I agree with this. I am currently working to move from PowerQuery data sources to Delta and it is really hard to know what is dependent on a specific data source and table. To make it easier, I would suggest that a table can be be selected and then all downstream dependencies in several levels are shown.
RE:
I was about to raise the same idea as I already have users for multiple clients who mistakenly forgot to populate the Gen Bus. posting group in Item journal and Item reclass journal and that lead to incorrect postings to the GL. I would suggest to either make the Gen. bus posting group available in Transfer order so users are forced to make a conscious decision while selecting the Gen bus posting group OR we can use a default Gen bus posting group specifically for Transfer order that can be populated in Inventory setup. That way wouldn't need to have a BLANK combination of Gen Bus posting group in General posting setup.
RE:
Would be amazing to be able to have this as a usable section for Business Central. I was investigating it's use to apply it to notify admins of the system if API access tokens were close to their expiration to re-authorize an application integrated with BC.
RE:
Hello,It should be awesome because we have more and more customers complaining that is not standard.Moreover, this is legal in Belgium so it should be covered if the multi-territoriality is proposed out of the box in the solution :)Thank you,Best regards,Olivier
RE:
Submitted in 2021, planned for 2023 release and now we are 2025 and we are still manually updating apps one by one, environment by environment, customer by customer, living like it's 1995.
RE:
planned for 2023 wave 1 ...
RE:
This is a very important feature for any EU deployment as people can change shipping address easily. We run exactly into this issue and the only workaround we found was to use a generic account per country: somehow in this case BC selects the proper customer account based on the shipping address. However, this makes it more difficult to keep track of the customer's information as there is one generic account per country and is not suitable.
RE:
Completely Agree!
RE:
We don't know why this is not changed?!!!We're now adding fields to the fieldgroup and then loading the values we need within the onaftergetrecord trigger fieldgroups { addlast(Brick; "Scanner Text 1", "Scanner Text 2", "Scanner Text 3", "Scanner Text 4", "Scanner Text 5", "Scanner Text 6", "Scanner Text 7") { } }
RE:
We're also trying to insert columns that are defined as URL in email templates, but that no longer works (it used to work in the past, but no longer does).A specific example is a Lead email template that contains a dynamic text placeholder for a column on Leads called "Download link" (text column of type URL) containing the URL for specific whitepaper to download. In the emails generated from the use of that template the URL is then included as text, but not as a clickable URL.