0
Category:
STATUS DETAILS

Comments

You can do this with a process in the meantime. Multiple required, or one if you're looking to alter all at once.

New field in work order : Update task percent
Type Number
Field editable

Control Option:
New field in work order
Simple Two options Yes/No
Name: Update % Complete

For ALL At Once
New process
Type: Workflow
Entity: Work order Service Task
Check condition
Work Order Service Task | % Complete | Contains Data
Work Order | Update % Complete | equals | yes

Add Step
Update Record
Work order Service Task

Set Properties:

Right Pane - > Operator : Set to
Look For: Work Order
Field : Update task percent
Select ADD

Click on % Complete and press OK

Category:

Same here. I've already spent days in finding and implementing different work arounds for this behaviour. Several of our customers were not happy with it. Could be so easy...

Category:

I would go further than this.
I'd like to see when you create a template, you specify the primary entity the template is focused on, and then the relationship to the Contact that should be the recipient.
Email processing is then based on the primary entity, allowing you to navigate up and down to include related information in the email.
You could then use it for transactional emails on the Event Registration record for event based emails, navigating down to get event details, or up to get the list of sessions the Event Registration covered.
But this then goes to cover Emails regarding any record which features a contact lookup (most of the emails we ever want to send are to a Contact regarding something), not just limited to Events.
Thanks

Category:

Certain organizations will not approve Microsoft Teams as a secure and viable solution. Currently the only alternative for members of those organizations is to @mention a huge number of users in every single post (including all replies) they make. It ultimately dissuades users from embracing Dynamics as a solution because generic e-mails remain significantly more efficient for larger teams. This is a bigger enabler than the votes indicate.

Category:

Excellent idea. Every single project I've been on that utilized the AWMS always complains about these orphan shipments/loads and always asks if there is a cleanup function to deal with them. 👍

Category:

This is especially important since we are urged to break up monolithic apps into smaller ones. Imagine having apps neatly broken up, ending up with two apps A and B, and one for the interplay (such as adding a B field to an A table) that is depending on them both: AB. Now if you're exposing the data of these apps via APIs, and you want to support A and B to be used both independently (which is the idea of having them separated) and combined (with the AB app on top of them), you would need API pages for A tables and for B tables, but as soon as you want to expose the B field that is added to the A table, you would also need to create an exact copy of the API page for the A table with just one B field added to it. That doesn't make sense.

If only we could
- add new fields to an API page, or
- allow extensions with the same prefix to extend API pages, or
- in some other way allow another extension to extend an API page

Category:

Would be a massive win to the product and solve so many situations where custom build is required to pre-populate tasks and activities when records are created.

Category:

Our customer also want the "additional information" captured in the vouchers description.
Unfortunately now the placeholders %4 %5 %6 are fixed variables which is different behavior as the other transactions.

Category:

I've found its already possible to view all notes created in a custom view, via the Record Type Notes.

Unfortunately there is no module to allow this saved view to be displayed, either in a table or dashboard.

Category:

Some of our clients also require this informations for the XSD and the XML file

Category: