web
You’re offline. This is a read only version of the page.
close
  • Provide masking of the credit card number when credit card number is used as CardID

    In release 1611, the credit card number is masked so only the last 4 digits are shown,. In July2017, this feature was removed. This is causing issues for my company. We use the credit card number as the Card ID, but do not want the entire number to show. http://www.dynamicconsulting.com/whats-new-or-changed-in-d3fo-july-17-update/ EXPENSE MANAGEMENT: CONFIGURATION RELATED TO EMPLOYEE’S CARD ID In prior releases, the employee’s expense credit card ID was designed to only allow up to 10 characters and displayed the last 4 digits entered as the card ID. The ability to enter more characters was required for organizations that have an agreement with their credit card company to use another key to identify an employee’s credit card number without entering the credit card number. This key is often greater than 10 characters and is typically between 20 and 30 characters. This feature has lengthened the Card ID field for the employee’s credit card setup (Human resources > Workers > Employees > Expense tab > Credit cards) and provides a parameter to validate whether a 15- or 16-character number is allowed as the card ID. The parameter, Enter employee credit card number, is found on the General tab of the Expense management parameters form (Expense management> Setup > General > Expense management parameters). By default, credit card numbers are not allowed as the expense credit card ID.
  • Provide OOB ability to store attachments to Sharepoint/Azure for D365 for Sales

    Provide OOB ability to store attachments to Sharepoint/Azure for D365 for Sales Or Provide OOB ability to prevent attachments being attached to Notes and other documents. This request is to help with providing and supporting a consistent experience for users when Sharepoint/Azure is used for document storage from CRM.
  • Provide consistent user experience by providing "Document" functionality inside main forms for entities

    To provide a consistent user experience, please provide the ability to put the "Documents" functionality on the Main form for entities that are configured to store documents on Sharepoint Online/Azure. Right now it is out of their normal process to click on the down arrow next to the record name, and click on Documents. Being a process they may not do every day, it could lead to repeated questions and frustration for the users. We already have the repeated questions and frustration for usage of Connections. Because of that, I believe it is not being utilized as it should.
  • Update documentation for copy Tier 2 to Tier 1 environment to include proper timing of applying customizations.

    We recently followed the instructions to copy a Tier2 to Tier1 on page: https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/database/dbmovement-scenario-exportuat#known-issues The instructions do not specify where customizations should be applied to the target environment. We have successfully applied customizations before the database restore, AND, after the database restore. Please update the instructions with the appropriate time to apply customizations to the target environment. Thank you :)
  • Provide Notification List for Cloud-Hosted environments in LCS.

    At this time, when a Cloud-hosted environment is serviced, only the project owners are notified of the service and status. Please provide a way to add email addresses to the Cloud-hosted environment description for additional people to notified when the Cloud-hosted environment is serviced. This would be much easier to manage, than adding project owners simply for notifications. It is understood the advance notifications sent for Microsoft Hosted environments may not be possible.

  • Activate Activities on Product Entity

    Please enable the ability to enable Activities for Entity Product. This will allow timeline for Product. Would be especially useful for PSA when creating new Products in Project.
  • Provide way to identify licensed users to Customer Engagement in the Customer Engagement App

    Need way to identify within Customer Engagement app, the users who are licensed users.
  • Assign Bookable Resource when Resource Assignment is assigned

    When assigning a Resource Assignment Record: If the current owner of the record matches who the record is being assigned to, the bookable resource is not updated. If the current owner of the record does not match who the record is being assigned to, Microsoft updates both the owner of the record and the Bookable Resource. Please change the code so that when a user assigns a Resource Assignment record, the Bookable resource is also updated every time. This will provide a consistent experience for the users, and increase productivity by saving the user from having to perform the extra steps to get the bookable resource assigned.
  • Please add ability to convert PDF and Word documents created in Customer Engagement to Excel retaining format

    Customer Engagement provides the ability to produce documents using word templates in PDF or Word form. Please provide a way for us to take those documents and convert them into excel worksheets. I have tried the suggestions online for converting the documents, but the format is not retained, and the excel worksheet is not useable. This would save our sales reps a lot of time for those customers that have special requirements for their quotes, and need to receive our quotes in excel format for upload to their systems.
  • Bulk Edit for Account Entity from Advanced Find - uses form not known or controlled by Customers

    Bulk updates to Account records via Advanced Find used to be huge time saver for Users. Users would specify their own criteria for Account records to update, and update in bulk on a form that is defined and enabled in the environment. Now, we are presented with a form we have no knowledge of in the environment, and have no control of. This is a relatively new change made by Microsoft. Microsoft has also verified this is by design. The current setup: - Forces users to create and save a new view in advanced find - Then exit advanced find - Then navigate to the Account Entity - Then navigate to the newly created view from the regular interface *The view is likely to be a one time use view. *Not a good use of users time and system resources I propose Microsoft restore the ability edit multiple records from Advanced find using a form known to and controlled by the customer.