Sometime user trying to delete a record from the customer master or any data that relates to financial dimension. So, user is facing above error upon deletion.
Error occurred because data exists in the table DimensionAttributeLevelValue
- Access the open the table DimensionAttributeLevelValue
- filter the record by Display Value field with the desired record to delete like customer number or employee number etc etc
- Select the filtered records
- Delete the selected records
- Then go back to customer master or where you facing the error
- Now try to delete you will be able to delete
AX 2012: you can directly delete the record by opening table
D365 : you can delete by access the SQL or write the runnable class to delete
Scenario: Sometime we need to uninstall a deployable package from the UAT or Production environment.
Below are the steps that need to be performed to uninstall a package.
- Create a deployable package using visual studio or Build server
- Do not extract the deployable package that is in ZIP folder (If you extract the zip folder you will face issue invalid HotfixInstallationInfo.xml file)
- Just open the deployable package zip folder
- Go to Deployable package zip folder -> AOS service -> Scripts folder
- create a text file name ‘ModuleToRemove’
- Write the module name to be removed in the the ModuleToRemove file
- If you have multiple models to remove then write mode name per line as below
- Note: In multiple models removing write the models name in sequence as per dependency sequence
- Go back to main zip folder and find the file HotfixInstallationInfo.xml ,copy the file to some other location and edit the file like below
- Edit the file should be same as above.
- Copy and replace the HotfixInstallationInfo.xml file in the deployable folder
- upload the file in the asset library and apply the package to the UAT environment first if applied successfully then apply to the production environment.
Please leave comments if you are facing any issue.
Below are the steps to connect Power BI with Microsoft Dynamics 365 for Finance and Operations
- Download and install the Power BI Desktop
- Sign in with the Licensed account
- In Power BI desktop ribbon click on Get Data
- Select OData Feed
- Enter the URL of the environment
- example is https://operations.dynamics.com
- At the end of the URL add /data to download the tables
- URL should be look like this https://operations.dynamics.com/data
- Enter the credentials of the user account in AX/D365. Organizational account account should be better rest base upon the requirement.
- Once everything done , next step is downloading the tables based on the security rights and privileges of the user.
- Now you can select the table from the list and start working on it for your workspace.
Follow the steps to connect and do let us know if you are facing any issue.
Scenario: Sometime a requirement to change the report name in the email thru print management need to change dynamically.
Class name where changes need to be done.
Report name update in the email
check the report name in this method and update the file name as per requirement.
Report name update in the PDF and screen viewer
- check the report name
- check the conditions for file and screen viewer
- update the file name for file condition
- update the file name and caption for the report
For Dynamics 365 for finance and operations use the post events of both methods
Below are summary about the new update of Microsoft Dynamics Finance and Operations apps version 10.0.7
- Budget Register Entry Enhancements
- Ability to export records from the accounts payable invoice pool
- Ledger Settlements by User
- Forecast position reports(Public sector)
- Mark a Purchase agreement as closed
- Users can now mark a Purchase agreement as “Closed” to signal the agreement is no longer actively used, making it so users will not be able to create release orders from the purchase agreement.
- Delayed Tax calculation on journal
- Reverse Journal posting
- Stop workflow submission when there are unallocated charges on a vendor invoice
- Account group selection for Chinese voucher types
- Sort resource in the project by invoice proposal
- Run Settle and post sales tax in batch mode
- Tax engine GTE (only available for India
For more details visit Microsoft Documentation using below link
Entity relationships are metadata. Entity relationships define the different ways of entity records can be associated to different entity records from other entities or the same entity. Entity relationships allows the query to retrieve data efficiently.
Types of Entity relationships:
There are two types of entity relationships
Many related entity records associated with a single entity record (1:N) ,a parent/child relation.
Many entity records are associated with many other entity records. A N to N( N:N) relation.
Entity relationship (1:N) do the following tasks, other than define the relations between the entities:
- If record deleted on the parent entity then the record associated in the child entities also deleted.
- When assign a record to a new owner, associated records also assign to the new owner.
- How the record and related records will be visible to the users.
Data is stored in the Common Data Service database is defined as entity. Entity corresponds to a database table and each field within an entity represents a column in that table.
Common Data service, metadata(data about data), is a collection of entities. Entity metadata controls the kinds of records you can create and type of actions performed on them. When we create or edit the entities,fields relationships, we are editing this metadata.
Common data service comes with a number of standard entities that support the core business applications.We need to become familiar with the catalog of standard entities.
For minor changes we don’t need to create new custom entities:
- To change the field display name or label we don’t need to create custom entity.
- We cannot delete the standard entities but we can hide them by changing the security role assignment.
Common Data Service allow you securely store and manage data that is used in the Business Applications.
Data within common data service is stored within set of records called entities. An entity is a set of records used to store data, similar to how a table store data within the database.
Azure Logic apps is a cloud service that helps
the tasks, business process and workflows when you need to integrate apps, data, systems across the enterprise and organizations.
Logic apps simplifies how you build scalable solutions
- App integration
- Data Integration
- System Integration
- Enterprise integration
whether on cloud or on-premises or both
Example of logic apps
- Send Email notifications from Office 365 when event happen in various systems, apps and services.
- Move uploaded files from SFTP or FTP server to Azure Storage.
- Process or re-route orders across on-premises system or cloud service.
- Monitor tweets with specific text words or lines.
- Create records on different system based on event happens on one system.