In Dynamics 365 for Finance and Operations you can select contact information on a worker to be private:

Once this private option is selected only users that have specific security roles can view this private contact information.

You can manage and control which security roles have access to this information by using the Global Address Book parameters>
Private location security:

Users that are assigned the selected roles from that parameter setting will be able to view the private contact information.

The post Private contact information viewable in Company Directory appeared first on Microsoft Dynamics 365 Blog.

When trying to apply a payment to an invoice in Dynamics 365 for Finance and Operations a person with a cross icon is displayed on the Settle transactions form. Typically, you could click on Inquiry> Specifications to see the transaction it is marked against. If this is blank you are not able to unmark the transaction to mark it again correctly.

To resolve this issue, you need to can now run the Consistency Check (System Administration> Periodic Tasks> Database> Consistency check) and selecting the Payments option. This allows users to unlock these transactions for them to be marked again to be settled. This consistency check will identify and clean up the orphaned settlement (SpecTrans) records.

For previous versions of AX you can find information on how to resolve this by following KB 894412: https://support.microsoft.com/en-us/help/894412/a-red-hand-symbol-appears-next-to-an-invoice-in-the-open-transaction-e

If you do not see the Payments option in the Consistency Check form please download KB 3187699 via LCS: https://fix.lcs.dynamics.com/Issue/Resolved?kb=3187699&bugId=3776531&qc=32c247d250343e3ddf31e7f5d74bff96793abd51d340836f4bc3608d95ac05a6

The post Unmarking locked transactions appeared first on Microsoft Dynamics 365 Blog.

We now have a Dynamics 365 Ideas Portal for you to log any new ideas for Dynamics 365 for Operations: https://ideas.dynamics.com/ideas/dynamics-operations

Like Microsoft Connect, you can view other suggestions, vote for or against an idea and add comments.

If you want to see what has the most votes, there is a hot tab plus there is a new tab to quickly see the latest ideas posted. You can also filter by status and time:

When you enter the site the Quick Links allows you to filter to see all the ideas under each module:

You can select “My feedback” to see a detailed view of ideas that you have submitted, the status and the total votes received.

Please take a read through the Posting Guidelines and FAQ on the Ideas Portal for more information.

Please note that suggestions that were previously entered under the Dynamics ERP Feedback product in Microsoft Connect have been migrated over to the Ideas Portal. These are displayed as created by Microsoft.

The post What would you love to see in Dynamics 365 for Operations? Post your idea on the Ideas Portal appeared first on Microsoft Dynamics 365 Blog.

In Dynamics 365 Operations (AX7) if a financial dimension contains the same character as the chart of accounts delimiter you may experience some instability.

The Chart of Accounts delimiter is set on the general ledger parameters and once this is setup the field is greyed out. (Previously this field was located in the system parameters)

An area we have seen customers encounter issues in is within a General Journal. For example, in a general journal when entering dimensions in the account field, you may select a Main Account followed by a Subproject. If the chart of accounts delimiter and the subproject both contain dashes you may experience an error in the journal when selecting this subproject dimension value of “Dimension value xxx does not exist”. Screenshots of this example are below for your reference.

Please see this link: https://ax.help.dynamics.com/en/wiki/planning-chart-of-accounts/ where it refers to this potential issue:
Create the chart of accounts on the Chart of accounts page. Main accounts can be created from the Chart of accounts page or the Main accounts page. Your main accounts shouldn’t use any special characters that are used as chart of accounts delimiters. If you do have a special character that is the same as your chart of accounts delimiter, you may experience instability, or the need to always use lookups or the flyout when entering account and dimension combinations.

We are currently working on a solution to this however in the interim we recommend not using the same special character in the chart of accounts delimiter and in financial dimensions.

If you do find yourself in this situation with data already in the system, you could work with your developer to change the chart of account delimiter to avoid this issue.

For your reference please see screenshots of an example of this scenario:

A subproject 000185-01 contains a dash as the subproject ID format “-##”

This subproject is listed as a valid financial dimension value

Projects is part of the active account structure

When entering a General Journal using this subproject as the financial dimension an error of “Dimension value XXX does not exist” is encountered.

A further error is seen when posting the journal of: Some of the information that you have entered is not valid. You must enter valid information before you can continue.

The post Financial dimensions that contain the same character as used in the chart of accounts delimiter appeared first on Microsoft Dynamics 365 Blog.

In this blog I am going to describe the setup required for automatic allocation examples that can be used within Budget Planning:

• Distributing budget plan lines from a parent to a child budget plan
• Copy budget plan lines from one scenario to another using Period Allocation
• Allocating budget plan lines monthly also using Period Allocation
• Aggregating child budget plan lines to the parent budget plan

1. Budgeting> Setup> Budget Planning> Budget Planning Configuration
   Scenarios within demo data will be used, Baseline and Forecasted
   
   
   
2. Stages within demo data will be used
   
   
3. Workflows
   Create a Parent Workflow with Stages: Initial and CFO review
   
   
   
4. Create the Child Workflow with Stages: Distribute, Submitted, Ready for approval and Approved
   Require parent budget plan: True
   
   
   
5. Scenario constraints
   Ensure that the Parent and Child Workflows have access to edit at all stages that will be used for both the Baseline and Forecasted scenarios
   
   
   
6. Period allocations
   General ledger> Setup> Periods> Period allocation category
   Monthly period allocation – will distribute budget amounts by the specified monthly percentage
   
   
   

   No change period allocation – will be used to copy lines from one scenario to another
   
   
   Note – See this TechNet article for more information on Period Allocations https://technet.microsoft.com/en-us/library/aa582352.aspx

   
   

7. Budgeting> Setup> Budget Planning> Budget Planning Configuration> Allocation Schedules

   Add
   Allocation schedule: Distribute
   Allocation method: Distribute
   Source Scenario: Baseline
   Destination Scenario: Baseline

   Add
   Allocation schedule: Copy Baseline to Forecasted
   Allocation method: Allocate across periods
   Period key: 40
   Source Scenario: Baseline
   Destination Scenario: Forecasted

   Add
   Allocation schedule: AggregateBaseline
   Allocation method: Aggregate
   Source Scenario: Baseline
   Destination Scenario: Baseline

   Add
   Allocation schedule: AggregateForecasted
   Allocation method: Aggregate
   Source Scenario: Forecasted
   Destination Scenario: Forecasted

   Add
   Allocation schedule: MonthlyBaseline
   Allocation method: Allocate across periods
   Period Key: Month
   Source Scenario: Baseline
   Destination Scenario: Baseline

   

8. Stage allocations

   Add
   Budget planning workflow and stage: Parent workflow, Initial
   Allocation Schedule: Distribute

   Add
   Budget planning workflow and stage: Child workflow, Submitted
   Allocation Schedule: MonthlyBaseline

   Add
   Budget planning workflow and stage: Child workflow, Ready for approval
   Allocation Schedule: Copy Baseline to Forecasted

   Add
   Budget planning workflow and stage: Parent workflow, CFO Review
   Allocation Schedule: Aggregate Baseline

   Add
   Budget planning workflow and stage: Parent workflow, CFO Review
   Allocation Schedule: Aggregate Forecasted
   

9. Budgeting> Setup> Budgeting workflows
   Create new> Budget Plan workflows

   Parent Budget Plan with elements in the following order:
   Start
   Activate associated budget plan
   Budget planning stage allocation
   Review associated budget plan
   Stage transition budget plan
   Budget planning stage allocation
   Review budget plan
   End

   
   Activate

   Create new> Budget Plan workflows
   Child Budget Plan with elements in the following order:
   Start
   Stage transition budget plan
   Budget planning stage allocation
   Review budget plan
   Stage transition budget plan
   Budget planning stage allocation
   Review budget plan
   Stage transition budget plan
   End
   

10. Budgeting> Setup> Budget plan> Process

    Select the Budget Cycle, Ledger, Attachment Folder and Organization Hierarchy being used

    In this example, Finance Department is the top of this Organization Hierarchy, thus will be assigned the Parent Workflow
    All other Departments and Business Units are assigned the Child Workflow

    With the Parent Workflow selected in the stage rules, the Initial and CFO review stages must have Associate budget plan, Add lines and Modify Lines selected, as well as a valid template assigned.
    

    With the Child Workflow selected in the stage rules, the Distribute and Approved stages needs to have Associate budget plan, Add lines and Modify lines selected, as well as a valid template assigned.

    The stages of Submitted and Ready for approval need to only have Add lines and Modify lines selected, as well as a valid template assigned.

    

11. Create a budget plan using the DEMO Allocations Process
    Add lines that include the dimensions used within the Organizational Hierarchy
    

    Submit Parent Workflow

12. Child budget plans are created for the Sales and Marketing Department and IT Department are created with the values apportioned monthly as set in the period allocation key.
    
    Complete the first review for each child budget plan
13. After the first review, the budget plan lines from Baseline scenario are copied over into the Forecasted scenario and the stage has progressed to Ready for approval
    

    

    Complete the review stage and child budget plans are now approved with a document status of Finalized.

14. The parent budget plan needs to be completed as the Associated Child Budget Plans are finalized

    

15. The workflow will now aggregate the Child budget plan lines up to the Parent budget plan for both Baseline and Forecasted scenarios
    

    

16. The Parent budget plan is now reviewed, finalized and completed
    

The post Budget Planning using allocations appeared first on Microsoft Dynamics 365 Blog.