Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/copy-configuration

Explanation

See explanation below
Explanation:
Go to Navigation pane > Modules >General Ledger > Ledger Setup > Fiscal Calendars.
Click the New Calendar button.
In the Calendar field, enter a name for the calendar.
In the Description field, enter a description for the calendar.
In the Start of fiscal year field, select April 1st.
In the End of fiscal year field, select March 31st.
In the Length of period field, enter 1.
In the Unit field, select Year.
Click the Create button to create the calendar.
Reference:
https://docs.microsoft.com/en-us/learn/modules/create-fiscal-calendars-years-periods-dyn365-finance/3-create

Reference:
https://docs.microsoft.com/en-us/dynamics365/unified-operations/dev-itpro/office-integration/use-excel-add-in
Topic 1, Relecloud Case
Background
Relecloud is a cloud point of sale (POS) software company specializing in direct to consumer food stands.
They have multiple business units using their new Dynamics 365 Finance and Operations implementation including customer-facing representatives for account management, technical support, customer service, and finance. There are two legal entities, one for operations and one for financials. Customers pay for the Relecloud POS software monthly and everything is deployed in the cloud. The Dynamics instance URL is
https//relecloud prod operations.dynamics.com.
Munson's Pickles and Preserves Farm is a company that uses Relecoud's cloud POS software to sell their produce in farmers markets. Munson's was one of Relecloud's first customers, and Relecloud stocks their employee lunchroom with Munson's products. Munson's has also been subcontracting their employees to Relecloud to help functionally build a best-in-breed solution. Munson's employees assume multiple organizational positions. Each employee has only a single email address by which people can contact them.
Current environment: System and IT
* Dynamics 365 for Finance and Operations was recently updated.
* All recurring batch jobs in the system were removed and recreated.
* The alert notification batch processing was recently changed from every 10 minutes to once every two hours.
* Real-time reporting of the information is not needed.
Current environment: Customer Service
* Customer credit requests are entered through the customer service team.
* All requests must contain a date, time, reason for request, and customer service notes on initial recommendations for credit action.
* Customers have multiple points of contact who can enter support tickets to the Relecoud portal.
* Tickets are automatically generated in the support team's third-party system when they are created by support technicians.
* The Dynamics 365 email client mail is used to correspond with customers.
Current environment: Technical Support/IT
* The technical support team gets involved when technical issues arise with the Relecloud software.
Service tickets are entered and get escalated to the team, depending on the issue.
* Microsoft Flow is used for automating different workstreams.
* Workflows are not configured for the technical support request flows in Dynamics 365 Finance and Operations.
* Management and history of technical support tickets are handled in a third-party issue management solution.
* The technical service team manages issues related to the Relecloud POS as well as the Dynamics 365 application.
Current environment: Account Representatives
* Each customer is assigned a single account representative.
* Account representatives use multiple devices.
* Only account representatives have the ability to approve credits.
* All email to customers come through their own Outlook instance.
Current environment: Finance
* Customers do not have invoice accounts.
* Only finance resources have the ability to enter credits.
* Credits can be entered by any of the four finance resources assigned the Credits and Refunds security role.
* If the request has not been updated in four days, the request is escalated to the Controller. The account representative must be alerted when this occurs.
Requirements: Technical support/IT
* Support technicians must use Microsoft's existing knowledge base to resolve open issues.
* If an issue exists, support technicians must report the status of the issue on a weekly basis.
* If there is no existing support request, support technicians must create one for Microsoft evaluation.
* All software must be installed centrally when possible.
* The Dynamics 365 Finance and Operations production environment must have an update cadence of every second Saturday from 4-7 A.M. EST.
* Updates must be tested in separate environment.
Requirements: Account representatives
* Account representatives must be able to see only the relevant customer fields and records automatically from their dashboard.
* Account representatives must be able to export the list of customers to Microsoft Excel.
* Account representatives must be able to navigate to the customer master record for any editing or record entry tasks.
* The forms must be relevant based on each account representative's needs.
* Account representatives need a centralized location to see multiple data components.
* Account representatives require an offline list of their current customers in Excel with only the fields they need.
* The IT Director must reassign all instances of an account representative's customer contacts if the representative leaves the company.
* An alert must be sent automatically to an account representative when a credit is issued or any data is changed on a customer's record.
Requirements: Financials
* Any refund must be printed as a physical check.
* All printers must be exclusive to the financial legal entity.
Issues
* Typing 'pickle' in the search box yields no returned results for the account representative.
* After the latest update, an account representative reports that he is no longer receiving alert notifications when a customer's contact is changed.
* An account representative has recently resigned.

Section: [none]
Explanation/Reference:
https://docs.microsoft.com/en-us/dynamics365/customer-service/configure-bot-virtual-agent