Microsoft Idea

on 04 Mar 2025 10:29:02

RE:

Currently, one journey only follows one specific time zone set for it.To send emails to different contacts at a specific time according to their time zones, users would have to create different journeys for different time zones.It would be highly beneficial for users to be able to configure email delivery so that messages arrive in contacts' inboxes at a specific time, such as 9:00 AM, in their respective time zones.

on 04 Mar 2025 10:29:02

RE:

Having an option that automatically applies time zones to our contacts would be beneficial. This will allow customer journeys to be sent based on the contact's time zone instead of the user's or default journey time zone.

Anil Khamkar on 04 Mar 2025 09:46:15

RE:

This is very basic scenario/functionality and should be part of a standard product.

Christian Hoffmann on 04 Mar 2025 08:10:32

RE:

Yes, please!

Jessica I on 03 Mar 2025 16:29:13

RE:

Can you please provide us with an update on this ? It is a must have functionality.

Jamie Constantine on 03 Mar 2025 15:01:17

RE:

This is a SERIOUS issue! this is a true microsoft BUG!!! please , @microsoft developers, look into this. I will be submitting a ticket! How can you allow a project to post dimensions from the project planning lines that will not post correctly to the GL!?!?!?!

on 03 Mar 2025 11:26:12

RE:

High value, low effort—it should be a must. :) I agree with Mark; integrating this information within a workspace would be very useful.

Mark Barlow on 03 Mar 2025 10:22:08

RE:

Great idea, and essential for efficient exception management when using Invoice Capture/AP automation. It would also be good to enhance the workspace to include different "buckets" for classifying invoices which are blocked.

Tarek HARAOUBIA on 03 Mar 2025 10:14:18

RE:

What about the annoucement of the availability of this feature ?

Vikrum Jaitly on 03 Mar 2025 09:30:37

RE:

Some of the issues have been resolved in D365. For example - Database log can record more than 10000 lines now.Entity has also been updated now from DAT to our Company's entity. However, in case of Table 20717 (General Journal Entry) data is still getting recorded in DAT entity instead of our Company's entity. Secondly, as per our Auditor's Concern, the Audit Trail of the entire D365 F&O should be visible and activated in D365.Following is the exact categorization of the issue:ISSUE: Requirement of total listing of tables available and assessment of classifying them ‘Into’ and ‘Out-of’ books of accounts. BUSINESS IMPACT: Requirement of total listing of tables available and assessment of classifying them ‘Into’ and ‘Out-of’ books of accounts. Analysis: we would like to know the total listing of tables available and assessment of classifying them ‘Into’ and ‘Out-of’ books of accounts and the customer wants to what tables s are available and what tables are mandatory in the Audit.