Comments
User an Email Template against the User entity, then reference the fields related to the booking.
Needs a new field in Work Order for Case Created.We have a report we run for a customer where this data is needed. To manage by an SLA's only on the Work Order entity would be the best solution.The SLA's could then start from the new Case created On field or Work Order Created On within the Work Order entity.
This is a critical feature for us use Fabric in production capacity. Please advice on timeline for a fix and/or workaround.
We have solutioned this with some extra fields on form, then a flow to create the extra requests until end date is reached Monday to Friday each week.
Functional Locations may provide the required solution
This would be a massive help. Users often find duplicate assets, if both of them have associations to transactional records it is a pain to 'merge' them as so many records are involved.
We have had failures due to a user that activated an Agreement no longer being a User, so the system job fails when it runs x months later. It is not easy to find these failures. The system jobs should not be running against a user, but should be system owned jobs in my opinion.
Create a new field of type calculated, then set the value of that new field with a calculation from the standard duration field divided by 60 for hours etc. Then use the new field where you want a value fixed in hours for example.
This could be done with a Power Automate flow to update the User Settings of a new User.
yes, I aggrege with this comment. it can be resizable window for the end-users