90
Currently if a Partner is to setup a Job Queue Entry it needs a user of the tenant to start this. This causes frustration with the Users because we need to ask them to get those started just for testing and also if there's an error they need to start it again.
STATUS DETAILS
Completed
Ideas Administrator

Thank you for this suggestion! We are planning to deliver on this idea with our coming release. Partners will be able to create and run the Jobs once, to validate that they can run without issues, then they will pass it to a licensed user to start the job recurrently. Find out more here: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/delegated-admin#restricted-access-to-business-central-as-delegated-administrator

Best regards,
Dmitry Chadayev
Business Central Team

Comments

M

Hi,


The problem is the unavailability to run as a different user. While creating a job has the user id of a consultant or employee as default then I claim that it should be possible to run with a different user. Specially this is a problem with interfaces where some employee has restarted a job where it should have been a special "interface" user id. Also this is important for job queues to run code and interface to other systems with a special user then it is not smart that the user id = employee.


On the other hand Elbek & Vejrup A/S has an app Extended Job Queue to solve this user name issue.


Just make it possible to configure and restart the job entries without changing the User ID. It should not be a big development task.


Go fix asap :-)

Category: Tenant Administration

M

This is a particular problem when configuring or testing the D365 Connector.
We have to "borrow" a customer license when there is any work around the connector as it relies so heavily on job queues.

There are also some "silent" issues that do not error but give unexpected results when the system attempts to create job queue entries for syncs and following record changes.

Some jobs (such as D365 connector) should run as some sort of service user or admin context, rather than a specific user. Which would resolve the issues with connector
Also allowing partners the option to start a job queue as another user ie "Run As"

Category: Tenant Administration

M

I am on the fence of that one. I don't want anything to be run under my user context in a customers environment. I think, it is a legit question to ask the customer to start a job queue, This is automation things and the customer should be aware of that anyways. So not having that feature is actually not a bad idea, since it puts responsibility where it belongs. On the customer side.

Category: Tenant Administration

M

I fully agree with this request, because we can't as the partner ask customer to make that for us.
It is mandatory to have ability to do that by ourselves
It is critical and blocking our job !
Best regards
Laurent

Category: Tenant Administration

M

Hello Team,

I second this idea please, as a partner it's not possible for us to set a job queue entry to "Ready".
This is kind of blocking and a source of confusion for customers; They don't understand why we have to go through them for this action.

And for setup/testing and all, it can be very annoying for them if we repeatedly ask to restart the job.

Thanks in advance.
Best Regards

Category: Tenant Administration