Comments
I fully agree, we are especially blocked by some colleagues who need to organise webinars by hidding names (as one can do in GoToWebinar or other pro systems) and they have started using Teams Premium but these options are not available when creating the Webinar from Dynamics 365 which is a major blocker and most of these users might simply stop using Teams and keep using GoToWebinar or Zoom.
@Nikola MIt is in the nature of things.see also here: https://vatdesk.eu/en/reverse-charge-mechanism/In the area of sales, only the assessment basis, i.e. the net amount, is reported to the tax authorities for reverse charge cases. This is why we in BC don't calculate VAT for this case and don't post any G/L entry for this. In purchasing, we have to report both the purchase VAT and the reverse charge VAT to the authorities. Therefore, we create a VAT entry and evaluate it twice in the VAT statement, once positively and once negatively. And we post the VAT amount in G/L as well:
@The BC Team"The F5 keyboard shortcut refreshes the data on the current page in Business Central. We would like to hear your feedback on why the F5 key is insufficient."The function to "Refresh" the page may need further clarification. The [F5] key is interpreted by browsers as a request to refresh/reload the entire page and its content. Sometimes this leads to only the parent page being loaded, the user being returned to the Role Center, or the BC Web Client throwing the "Something went wrong." error.For example:In BC23, one can drill down on the "No. of Records" field on the Table Information page. The information is presented in a separate browser tab. Pressing the [F5] key to refresh the record information reloads the entire page, which, in this case, results in the "Something went wrong." error.The way that I would interpret this idea is to add a "Refresh" page action that behaves the same as invoking CurrPage.Update() in code. The page action should be present on all pages throughout the application, similar to how it was in the NAV RoleTailored Client.
I have voted. Our team would like to see an increase in the size of the segment query. At the moment we are having to work around the current 4,000 character limit, however, when we get into more complex segments this creates an issue. The current character limit hinders the segments we need to build, therefore, it is crucial that this is prioritised.