Comments
Packages don't necessarily cover all the requirements of a License Plate. This is something required and quite common in the Supply Chain Realm. I've been working with Insight Works License Plates for over 4 years and while this application does come with good feature out of the box there are many gaps, which we've had to cover with custom workflows and development. Worth looking into if you are in need of an easy to install License Plate solution.
Today this is causing major issues in implementing upgrades for some big onpremise customers changing from legacy to the new UCI. Can't believe this has been reported over 5 years, recognized as a feature gap and still not prioritized. Fixing this is far more valuable that Copilot or an agent!
I agree. It’s very important for the dispatchers to see multiple days at once to plan properly. Right now, we are very frustrated and scheduling is almost impossible. It takes a lot of time and effort. The old scheduling board in Field Service was helpful and made planning easier. But since the new update, that’s no longer the case. The view doesn’t work for. Before the update, we could see 14 days at once, which was very helpful.
The provided solution of "run once (in foreground)" is a bandaid and more of a workaround. What we need is to be able to start job queue entries without the user changing. Perhaps credential authorization can be stored internally when the customer user initially started the Entry. I realize this would take more invasive changes, but it's the only thing providing an acceptable user experience.
I know this isn't really the forum to provide help. Especially on a topic 5 years old. But you could also evaluate to store historical and/or binary data (the two biggest contributors to database size) outside of BC. Either in Azure Data Lake or Azure Blob Storage. Both also have a much more economical price setting.