Maria Pencheva

Basque is a language spoken by Basques and others of the Basque Country, a region that straddles the westernmost Pyrenees in adjacent parts of northern Spain and south-western France.

Currently it is not one of the supported languages, integrating Basque language would help accommodate partners' current and future needs.

If an item has attached documents - image of the item, in case it is a BOM - a list of the materials, etc, when the item is chosen on a Purchase/Sales orders line and wanting to send email confirmation or invoice for the order, it would be of great use to be able to choose these images or documents by having them available in "Add attachments from source" when sending the email.

You can still add them manually from the local machine, which however when having hundreds of items could be quite time-consuming.

With the current system logic In the expanded permissions it should still be visible what permissions are excluded, as they show up with empty permissions in the list. If page 0 is included, any page that is not explicitly in the list with empty permissions would have permissions granted.

And that leaves a lot of space for ambiguity.

It would be nice to have a less complex function/practice to explode permission sets.

In Business Central it is not uncommon that you experience a mix of translations when an environment is deployed in a given localization and a different language is preferred and selected in the UI afterwards.

For certain pages, however, like the Workflow templates, the whole content is displayed in the localization language and shows the records from the table and not captions which have translations loaded by a language layer. And at the moment beside some special item translations module, records are not translated.

It is not uncommon too that users not ways speak the languages the environment has been localized/ deployed.

It would be great to have this logic alternated in the future in order to have all pages and tables presented in the desired by the user language.

Partners struggle with the current Job Queue error logging design.

If there is only one document being posted and if that contains some error, error is shown in the job queue and job queue stops.

While when multiple documents are being posted and some of them contains error, job queue shows success and errors are registered. 

This is troublesome because it is often needed that a job runs continuously every half hour and due to this behavior, it is not possible to implement such job queue entries without checking for an error.

It would be great to have the logic re-considered and changed in favor of having the same behavior for single and multiple postings when it comes to error logging.