on
RE:
Agreed with everyone else commented before. Why a basic functionality like is is not being implemented for so long.
RE:
Planning to share common tables from Warehouse with other workspaces. The warehouses are created with case-insensitive (CI) collation, then we create shortcuts on lakehouse the tables in lakehouse changed to case-sensitive again. So it is better to allow create shortcuts on Warehouse, so the other workspaces can be created with case-insensitive (CI) collation and accesss the data without any case sensitive issues.otherwise having one copy is not possible with current options.
RE:
We have the same requirements where we need physical dimensions on variant level
RE:
4-4-5 is still common in manufacturing and retail and this prevents such businesses from leveraging recurring journals! This would be similar to where comparison periods are needed in financial report column definitions. Recurring journals need to be able to support non-monthly financial periods when defined in the Accounting Periods page.
RE:
We are using f&o, which is integrated with project operation, so there is a challenge in restricting users from feeling timesheets while they are already on leave for that day because we are not getting leave data in project operation.This is a basic requirement that needs to integrate leave absence with the project ops time sheet, so users are restricted from feeling the time sheet on leave and the same for restricted users to feel leave and absence when they have already filled out the timesheet for the same day.
RE:
Agree - the displaying of the Tracking Token in the header gives email the appearance of SPAM or Junk email to customers. This perception is preventing our sales team from using/embracing the functionality of email with Dynamics.
