Archive for the ‘Dynamics 365’ category

Dynamics 365 Customer Insights is coming … ask Synergy Software Systems

August 18th, 2023

Microsoft will retire the product name Dynamics 365 Marketing and rebrand most of its current capabilities as part of Dynamics 365 Customer Insight.

Dynamics 365 Customer Insights, is an AI driven solution which will revolutionize customers experiences. For the two elements, of Data, and Journeys. “Customer Insights – Data” will be the name of the existing Customer Insights solution for a customer data platform that provides an organization with a 360-degree view of their customers. D365 Marketing will be known as “Customer Insights – Journeys”. the new offering will be available for purchase starting on September 1.

Combining both marketing and customer data under one brand aligns with Microsoft’s product vision, for Customers to run campaigns based on customer entities stored in Dataverse or based on profiles stored in Customer Insights from other sources. 

For existing D365 Marketing customers, the transition from outbound to real-time marketing will continue as part of the product change. Starting this month, new customers will only have access to real-time marketing capabilities. Existing customers can continue to use outbound marketing, but Microsoft will not be adding any enhancements.

(Microsoft’s 2023 Release Wave 2 plans still includes a section for D365 Marketing separate from Customer Insights.)

Microsoft to end new Dynamics GP sales and will move BC to subscription only licenses.

August 6th, 2023

Microsoft recently alerted partners of plans to end the sale of Dynamics GP to new customers over the next three years. Microsoft will stop selling new perpetual licenses for new customers Dynamics GP in October 2025, and the sale of new Dynamics GP subscription licenses for new customers will end in October 2026. The change effectively sets an end date for new customer sales of GP.

These decisions do not impact the ability of existing customers of GP and BC on-prem to run their systems, to add users, or to license capabilities.

This change doesn’t impact Microsoft’s plans for providing necessary regulatory/security/usability updates for Dynamics GP beyond this date. New customers seeking an on-premises ERP solution consider Dynamics 365 Business Central on-premises or Dynamics 365 for Operations on-premises, Enterprise Edition. 

Dynamics 365 Business Central on-premises solutions will move to subscription-based licensing only, ending the perpetual license option.

Subscription billing replaces revenue recognition in Dynamics 365 Finance

June 21st, 2023

Subscription billing enables organizations to manage subscription revenue opportunities and recurring billing through billing schedules.

Complex pricing and billing models and revenue allocation are easily managed, and are billed and recognized at the line level.

Multi-element revenue allocation enables allocation of revenue to comply with International Accounting Standards (International Financial Reporting Standard 15 [IFRS 15]) and Generally Accepted Accounting Principles (US GAAP) standards (Accounting Standards Codification Topic 606 [ASC 606]).

The solution has three modules that can be used independently. Alternatively, all three modules can be used together.

  • Recurring contract billing – This module enables recurring billing and price management to provide control over pricing and billing parameters, contract renewal, and consolidated invoicing.
  • Revenue and expense deferrals – This module eliminates manual processes and dependency on external systems by managing revenue and enabling real-time insight into monthly recurring revenue.
  • Multiple element revenue allocation – This module helps with revenue compliance by handling pricing and revenue allocation across multiple items.

Note the current revenue recognition module will be deprecated in October 2023, and since April 2023 is receiving no code updates/fixes.

Co-Pilot and Business Central ask Synergy Software Systems

May 23rd, 2023

This video guides you through the minimal steps necessary to get started quickly in creating a chatbot with expanded natural language capabilities inside of Business Central. Copilot provides AI-powered writing assistance for Business Central users responsible authoring marketing text (product descriptions) on items sold in online shops, like Shopify. With the click of a button, Copilot generates text that’s engaging, creative, and highlights key attributes of the specific item. With a bit of reviewing and editing, it’s ready to publish. Copilot in Dynamics 365 Business Central help small and medium-sized businesses to bring new products to market faster by producing AI-generated product descriptions.

April 24th, 2023

Microsoft 365 Copilot combines the power of large language models (LLMs) with your data in the Microsoft Graph and the Microsoft 365 apps to turn your words into the most powerful productivity tool on the planet.

Microsoft Graph is the gateway to data and intelligence in Microsoft 365. It provides a unified programmability model to access the tremendous amount of data in Microsoft 365, Windows, and Enterprise Mobility + Security. Use the wealth of data in Microsoft Graph to build apps for organizations and consumers that interact with millions of users. Custom applications can use the Microsoft Graph API to connect to data and use it in custom applications to enhance organizational productivity.

Microsoft Graph provides a single endpoint that the app can use to access the required data and to simplify the overall development process.

Organizations store vast amounts of data and intelligence across Microsoft cloud services, but how accessible is the data to users?

For example, a salesperson is setting up a meeting with a customer, wants to easily access files and previous meetings and notes but are those emails and chats between a salesperson and customer easy to find? What people within the organization can the customer contact for support?

Data and intelligence like the following types can be accessed through the Microsoft Graph REST APIs and client libraries:

  • Users and groups
  • Teams data
  • Tasks
  • Files
  • Mail
  • Meetings and calendars
  • Organizational charts

Copilot is an AI-powered tool that uses natural language processing and machine learning to understand users’ requests and provide personalized recommendations, tips, and assistance. Users can ask Copilot questions and get instant answers, guidance, and suggestions to help them work more efficiently.

Copilot is designed to be available across multiple Microsoft 365 applications, including :Word, Excel, PowerPoint, Teams and Outlook, and is intended to be context-aware. It ‘understands’ the user’s specific needs and the task at hand. Some examples of this functionality are the ability to point copilot to a word document, and request to create a power point presentation based on the data in the document.

Copilot will also work with tools from the Power Platform and Dynamics 365 products. Copilot for Power Virtual Agents is already in preview.

Copilot enables marketers to create targeted customer experiences and interactions that are informed by data-driven decision making. With access to the natural language data discovery feature in Customer Insights, they can build confidence by validating and discovering customer insights for their marketing strategies. For example, a marketer can ask Copilot how many of their customers fit the profile of currently residing in Washington, DC, who are over the age of 25, who have also attended a promotional event in the last six months.

With just a few clicks, Copilot will present the results of their query, including the number of customers that match the attributes or behaviors, as well as other useful information such as the customer lifetime value, product preferences, or average purchase price.

Copilot in Dynamics 365 Customer Insights removes the barrier of needing to craft queries in SQL to get a deeper understanding of customers, enabling marketers to speed and scale the delivery of hyper-personalized experiences that customers expect.

Copilot in Viva Sales

Automatically generate contextual email replies and meeting summaries with Copilot in Viva Sales, available to Dynamics 365 Sales customers. Copilot in Microsoft Dynamics 365 Sales and Viva Sales helps sellers dramatically reduce the time they spend on clerical tasks. AI helps write email responses to customers and can even create an email summary of a Teams meeting in Outlook. The meeting summary pulls in details from the seller’s CRM such as product and pricing information, as well as insights from the recorded Teams call. With sellers spending as much as 66% of their day checking and responding to emails, this presents a significant business upside to give the seller more time with their customers.

. For example, with Viva Sales, Copilot can learn how to connect to CRM systems of record to pull customer data — like interaction and order histories — into communications. As Copilot learns about new domains and processes, it will be able to perform even more sophisticated tasks and queries.

Copilot in Microsoft Viva Goals simplifies goal setting by guiding leaders through the process of creating objectives and key results (OKRs) as well as simplifying goal management across the organization. Copilot can suggest draft OKR recommendations based on existing Word documents, such as an annual business plan or a product strategy paper. Once created, Copilot saves employees time by summarizing the status of OKRs, identifying blockers, and suggesting next steps. Lastly, Copilot can consolidate existing data to generate more comprehensive check-ins so teams can leverage a breadth of knowledge across different sources of truth.

An entirely new experience is Business Chat that works across he Microsoft 365 apps, and your data — your calendar, emails, chats, documents, meetings and contacts — to do things you’ve never been able to do before. You can give it natural language prompts like “Tell my team how we updated the product strategy,” and it will generate a status update based on the morning’s meetings, emails and chat threads.

You will be able to access Business Chat from Microsoft, from Bing when you’re signed in with your work account, or from Teams.

Copilot will fundamentally change how people work with AI and how AI works with people. As with any new pattern of work, there’s a learning curve — but those who embrace this new way of working will quickly gain an edge. Copilot is integrated into Microsoft 365 and automatically inherits all your company’s valuable security, compliance, and privacy policies and processes. Two-factor authentication, compliance boundaries, privacy protections, and more make Copilot the AI solution you can trust.

I have only scratched the surface – Teams swept the business world during COVID now Co-Pilot and VIVA integrated across your favourite apps erps and crm systems – we often read about game changing software and paradigm shifts- but this times it’s for real and faster than we realise.

Power BI and end of support for Windows 8.1

April 6th, 2023

After almost 10 years, support for Windows 8.1 ended on January 10, 2023. Consequently support for Power BI Desktop on Windows 8.1 will stop on January 31, 2024.

After that, Power BI Desktop will only be supported on Windows 10 and newer.

The January 2024 release of Power BI Desktop for Report Server will be the last release to support Windows 8.1, and this version will only receive security updates until January 2025 per the Modern Lifecycle Policy.

Public preview release of the Asset Management mobile app for Dynamics 365 Supply Chain Management

March 29th, 2023

Asset Management is an advanced module for managing assets and maintenance jobs in Dynamics 365 Supply Chain Management. Asset Management integrates seamlessly with several other finance and operations apps.

The new mobile app is available for all commonly used mobile platforms, devices, and form factors.

The app enables maintenance workers to review their assigned jobs, mark tasks as complete, enter notes, and log the time and materials consumed. Other staff can use the app to quickly file maintenance requests by scanning a barcode, entering notes, and submitting photos.

The Asset Management mobile app is built as a Canvas app in PowerApps, and doesn’t require any additional licenses to use. The app leverages the security roles already established in Supply Chain Management to grant the appropriate users access to the maintenance request and/or job management functions as needed.

System requirements

To run the Asset Management mobile app, you must be running Supply Chain Management version 10.0.32 or higher.

The app is available for all commonly used mobile platforms, devices, and form factors.

 Launch of the new Microsoft Dynamics 365 Copilot 

March 7th, 2023

 Provide interactive, AI-powered assistance across business functions. With Dynamics 365 Copilot, organizations empower their workers with AI tools built for sales, service, marketing, operations and supply chain roles. These AI capabilities allow everyone to spend more time on the best parts of their jobs and less time on mundane tasks.

According to a Microsoft recent survey on business trends, nearly 9 out of 10 workers hope to use AI to reduce repetitive tasks in their jobs.

Customer relationship management (CRM) and enterprise resource planning (ERP) systems are mission-critical; however, these both frequently require burdensome tasks like manual data entry, content generation and notetaking.

Dynamics 365 Copilot uses recent advancements in generative AI to automate these tedious tasks to unlock the full creativity of the workforce.

This is not the first time Microsoft has used the term “copilot” in relation to its AI technology. When it announced in February that Bing was incorporating AI, the company said the search engine is now an “AI-powered co-pilot for the web.”

Dynamics 365 Copilot puts CRM and ERP can accelerate pace of innovation and improve business outcomes in every line of business:

  • Copilot in Microsoft Dynamics 365 Sales and Viva Sales helps sellers to dramatically reduce the time spent on clerical tasks. AI can help to write email responses to customers and to create an email summary of a Teams meeting in Outlook. The meeting summary also pulls in details from the seller’s CRM such as product and pricing information, and insights from the recorded Teams call.
  • With sellers spending as much as 66% of their day checking and responding to emails, this presents a significant business upside to give the seller more time with their customers.
  • Copilot in Dynamics 365 Customer Service empowers agents to deliver exceptional customer care. Dynamics 365 Copilot can drafts contextual answers to queries in both chat and email. Interactive chat experience uses knowledge bases and case history and this AI-powered expertise is always available to answer questions.
  • Customer service departments can now build virtual agents in minutes with conversation boosters in Power Virtual Agents,to harnesses the power of the Azure OpenAI Service and Bing to provide answers from company websites and internal knowledge bases.
  • Copilot in Dynamics 365 Customer Insights and Dynamics 365 Marketing empowers marketers to simplify data exploration, audience segmentation and content creation.
    • With Copilot in Dynamics 365 Customer Insights, marketers can curate highly personalized and targeted customer segments, using dialogue with their customer data platform in natural language.
    • Marketing staff can receive suggestions about additional segments not previously considered. This new capability can handle complex calculations and match customers that fit a select profile.
    • In Copilot for Dynamics 365 Marketing, marketers can describe their customer segment in their own words to create a target segment with the query assist feature.
    • Marketers can also use Dynamics 365 Copilot tfor inspiration for fresh email campaign content based on a simple request. Copilot makes suggestions based on: key topics entered by the marketer, the organization’s existing marketing emails, and from a range of internet sources to increase the relevance of generated ideas.
  • Copilot in Dynamics 365 Business Central streamlines the creation of product listings for online commerce. Use Product attributes such as colour, material and size to create compelling product descriptions for online storefronts in seconds. Tailor the descriptions and choose tone of voice, format and length. Business Central customers who use Shopify can seamlessly publish the products and their descriptions to their Shopify store in just a few clicks.
  •  Microsoft Dynamics 365 Supply Chain Management customers can access Copilot in Microsoft Supply Chain Center, to proactively flag external issues such as weather, financials and geography that impact key supply chain processes.
  • Predictive insights can then
  • surface impacted orders across materials, inventory, carrier, distribution network and more. Supply chain planners can automatically draft an email generated by Dynamics 365 Copilot to alert impacted partners and mitigate potential disruptions before they happen.

The next era of business applications is already transforming with generative AI. Users will increasingly expect their CRM and ERP applications to include AI-powered expertise.

The recent AI momentum incorporates the next generation of AI capabilities across Microsoft 365, Dynamics 365, and the Power Platform and includes::

  • Viva Sales, which helps sellers by bringing a sales copilot to their flow of work in Microsoft 365;
  • Power Apps, enabling citizen developers to write code using natural language.
  • Microsoft Teams, the collaboration platform for work with more than 280 million monthly active users; 

Dynamics 365 Finance – Tags – new feature

February 13th, 2023

Source: Microsoft

After transactions are posted, it’s common for organizations to require visibility into subledger data, to analyse the accounting entries. Organizations use fields such as the document number, description, or financial dimensions to track subledger data in the general ledger, because it’s difficult to navigate the data model to the subledger data.

The types of subledger data that are often tracked include sales order or purchase order numbers, vendor or customer names, payment references, invoice numbers, or reference numbers from external transactions that are imported into Microsoft Dynamics 365 Finance.

In addition to being used for analytics, the subledger data is used for processes such as ledger settlement.

The Financial tags (tags) feature eliminates the need to solely rely on document numbers, descriptions, or financial dimensions and an organization can now create and enter up to 20 user-defined fields on transactions. Those fields are then stored on the accounting entries that are created for the transactions.

Tag values aren’t stored in any subledger tables, nor in the Customer transactions or Vendor transactions table.

Tags were introduced in the 10.0.32 release of Dynamics 365 Finance. This release supports the capability to define up to 20 user-defined tags and to enter tag values on the following journals (and corresponding Open Data Protocol [OData] and Data management entities):

  • General journal
  • Global general journal

In subsequent new releases, tags will be implemented in additional journals, documents, and processes.


To use the functionality, enable the Financial tags feature in the Feature management workspace.

The feature can be disabled at any time. When the feature is enabled but later disabled, any values that were entered for financial tags on transactions will be maintained in the database. However, they’ll no longer be visible on any transactions or in inquiries in Dynamics 365 Finance.

Enter tags on transactions resembles similar to entry a ledger account that uses financial dimensions.

Tags don’t use the same control as a ledger account, but those still require a delimiter between the tag values, so define the tag delimiter before you define any financial tags.

  • On the General ledger parameters page, select Financial tags, and specify the delimiter.
  • The delimiter that you specify must not be used in any tag values that are entered on transactions. The delimiter can’t be changed after it’s defined.

After the feature is enabled, each legal entity can define up to 20 financial tags.

 Tags are legal entity–specific.

Use the Financial tag configuration and Financial tags custom list value entities to import the tags for each legal entity to quickly and easily define the same initial setup in multiple legal entities.

Create financial tags

Before you create financial tags, note the following points:

  • Evaluate whether the data should be tracked as a financial dimension or a financial tag.
  • Financial tags are an alternative to financial dimensions, especially when you’re tracking values that have little or no reusability, such as sales order numbers or purchase order numbers..
  • After a financial tag is created, it can be deactivated but not deleted. This restriction helps to ensure that the tag values remain available for reporting on posted general ledger entries. Financial tags can easily be activated and deactivated at any time.
  • The label of each financial tag can be changed at any time, even after transactions are posted.
  • If no transactions have been posted for a specific financial tag, then a change to the tag’s label will have no impact. This behavior is useful when you must repurpose a tag so that you can track other data.
  • When transactions are posted for a specific financial tag, the tag values don’t change. When the tag’s label was originally “Purchase order number,” but it’s later changed to “Sales order number,” the accounting entries that were posted before the label change will still contain the purchase order numbers that were entered and posted to the general ledger.

Create a financial tag

Follow these steps to create a financial tag.

  1. Go to General ledger > Chart of accounts > Financial tags > Financial tags.
  2. Select New to create a financial tag.
  3. Enter a label for the tag. The label must start with a letter or underscore, and it can contain only letters, numbers, and underscores. No special characters, including spaces, are permitted.
  4. In the Value type field, select TextList, or Custom list.
  5. If you selected List in the Value type field, select the value source in the Use values from field. The field contains a list of entities that the tag values can be selected from during transaction entry.
  6. If you selected Custom list in the Value type field, select Tag values to create the custom list of tag values that will be available for selection during transaction entry.
  7. Select Activate to activate the tag.

Enter financial tag values on transactions

After one financial tag is activated, tags are available for entry on each transaction that supports the feature.

Journals and lines

When you enter journals, define tag values on the journal batch header. Those values will be used as default values for the lines in the journal.

  • As for other default values in the journal, they’ll automatically be entered on new lines that are added to the journal.
  • However, these will not be entered on lines that already exist when you define the values on the header.

Default values

Tag values that you enter in a journal are entered as default values in the following way:

  • Single-line voucher:
    • Tag values that you add to the journal batch header are entered as default values on the account.
    • Tag values that you add to the account are entered as default values on the offset account.
    • If the offset account already exists when you add tag values to the account, then those tag values aren’t entered as default values on the offset account.
    • If tag values exist on both the account and the offset account, then changes to the tag values in one place don’t cause the values in the other place to be updated. For example, when you change the tag values on the account, the tag values on the offset account aren’t updated. This behavior helps to prevent loss of data should a user manually override the default values.
    • When you add a new line, and you assign a new voucher number (which represents a new transaction), the defaulting behavior starts over.
    • Tag values from the lines of one voucher are never entered as default values on the lines of a different voucher.
  • Multiline voucher:
    • Tag values that you add to the journal batch header are entered as default values on the account of each line that’s added to the voucher.
    • The tag values that you add to the account on the first line aren’t entered as default values on the account of the next line of the voucher, and so on.
Financial tag values on journal lines.

Tag values from master data are never used as default values. For example, there’s no capability to define default tag values on customers or vendors.

In addition, tag values from the transaction itself aren’t automatically entered as default values. For example, when a tag was created to track the customer name and subsequent transaction contains a customer, then the  tag value isn’t entered as the customer name by default. The value must be manually entered or imported.


When tag values are entered on transactions, no validation occurs during either transaction entry or posting.

Even when a tag of the List or Custom list value type is defined, the tag values aren’t validated to ensure that they exist in the list.

For example, a tag of the List value type is created, and the purchase order number is selected as the source of the list. Although a list of purchase order numbers will be presented, the user can still enter a purchase order number that doesn’t exist in the list.

Posting transactions that have tag values

After a transaction is posted, the financial tags are available on the lines of the general ledger account entry.

  • Those are shown on the Voucher transactions ,and the Transactions for main account pages.
  • The financial tags are shown in separate columns, so that they’re easier to sort and filter.

For reporting, the tags aren’t part of the dimension sets. Therefore, you can’t get a summarized balance of transactions for a specific tag value. For example, when you’re looking at the trial balance, you can’t get balances per tag value.

However, when you drill down into the balances from the trial balance, the tag values will be shown on the detailed transactions. The detailed transactions, including the tag values in separate columns, can be exported to Excel, where they can be summarized if balances are required.

When a tag is deactivated, the tag values remain on the posted transactions.

 By default, deactivated tags aren’t shown on inquiry pages. However, you can add the columns by selecting Show inactive financial tags.

Correct tag values after posting

Although financial tags are available for reporting, they aren’t part of the ledger account and have no impact on financial statements.

Because tags are used only for internal analysis, edits to the tag values are permitted after transactions are posted.

  1. In the Feature management workspace, enable the feature that’s named Allow edits to internal data on general ledger vouchers. This feature enables some roles to modify the Description field of posted accounting entries.
  2. If the Financial tags feature is also enabled, then this feature is enhanced to enable edits to the tag values.
  3. After the feature is enabled, go to Voucher transactions.
  4. Use the query to find the transactions that you want to edit.
  5. Select the lines in Voucher transactions, and then select Edit internal voucher data.
  6. You can edit only lines that are selected.
Editing tag values on voucher transaction lines.

The page shows the lines that you selected in Voucher transactions, including the current financial tags and new financial tags.

The current tag values are entered as default values for the new tags. Therefore, you don’t have to manually enter everything again but can instead change only what’s incorrect.

Use the Bulk update selected records button to do mass updates. Mass updates are useful to assign tag values to large groups of posted transactions that were incorrect or that no tag values were defined for (for example, because they were posted before the feature was enabled).

Example uses

  1. Stock # – Solar company or auto reseller wants to keep track of all the transactions for a specific unit throughout the life of an asset.
  2. Vendor accruals – Keep track of accrued expenses by vendor in the General Ledger, instead of maintaining Excel files outside the system to track Vendor ID for expenses coming through accrual entries.
  3. Lot – Expense tracking by specific lots, value add, etc. going directly through AP/GL
  4. Marketing campaigns – tracking marketing campaigns is not a perfect candidate for a financial dimension as you don’t want to keep adding too many financial dimensions. But Financial tags can serve this purpose to track expenses by marketing campaign.

Financial tag values used within D365 are not critical for financial reporting outside the company, but they can be important for the internal reporting by FP&A teams. These teams need the ability to make changes to transactions after posting rather than reclass journal entries.

Tags and Financial dimensions

Financial dimensions are used to code accounting entries for reporting (for example, to identify sales per department or expenses per cost center in general dimensions are primarily used to create a detailed P@Ls at the dimension level).

 Financial tags (tags) are not meant to be an alternative to financial dimensions. An organization can create up to 20 user-defined financial tags and enter values for these on transactions.

 Like financial dimension values, tag values are stored on the accounting entries that are created for the transactions. However, tag values aren’t stored in any subledger tables, such as the Customer transactions or Vendor transactions table. Both financial dimensions and financial tags can be used for analytical reporting, and also for some processes, such as ledger settlement.

Financial dimensions are very structured. The setup is used to control which dimensions are required, which dimension values are valid, and which dimension combinations are valid.

Financial tags have limited structure, no validation is done, and very limited defaulting is done.

The following table describes, in detail, the differences between financial dimensions and financial tags, to help organizations determine which feature they should use.

FunctionalityFinancial dimensionsFinancial tags
Account structuresDimensions must be included in an account structure before they can be used in a legal entity. The account structure determines the dimensions that are required for the main account and the valid combinations.Tags aren’t part of the account structure.
ValidationDimension values on the ledger account are validated against the account structures to determine whether the dimension values are active, the dimension combinations are valid, and the values exist.Tag values aren’t validated during transaction entry or posting.  Any value can be entered, even when the tag is defined as a tag of the List or Custom list type. A value doesn’t have to be selected in the list. There’s no way to require a tag value.
DefaultingDefault dimension values are entered from master data, such as customers, vendors, products, or projects. These are also entered from the header of a document to the lines. For journals, these are entered from the journal header to the account, and from the account to the offset account.Default tag values aren’t entered from master data. However, they’re entered from the header of a document to the lines. For journals, these are entered from the journal header to the account, and from the account to the offset account.
ReportingDimension values can be used for reporting in multiple ways. Dimensions can be included in a dimension set, which is used to calculate totals for the ledger account. Dimension values can also be viewed on each detailed transaction. The segments can be parsed out, and then used to sort and filter the detailed transactions.Tag values aren’t included in dimension sets. In Microsoft Dynamics 365 Finance, you can’t generate a trial balance to view balances for tag values. When you drill down from the balances on the trial balance, tag values are shown on each detailed transaction.  The tag values are in separate columns. Therefore, it’s easy to sort and filter on transactions in the Voucher transactions or Transactions for main account inquiry. The detailed transactions can be exported to Excel or Power BI.
Impact on General ledger processesAlthough dimensions are considered unlimited, the more dimensions that are created and used in a dimension set, the slower transaction entry, import, and processes will become.Because tags have no structure or validation, there’s minimal impact when they’re used on transactions or imported via an entity.
Non-reusable valuesDimensions should never be used to track non-reusable values, such as document numbers or reference numbers. This type of data will cause your chart of accounts to explode, because of the uniqueness of so many ledger accounts. Therefore, performance will be negatively affected, especially around the year-end close and during foreign currency revaluation and consolidations.Tags should be used to track non-reusable values, such as document numbers or reference numbers.
Ability to activate or deactivateNew financial dimensions can be activated, but the system must be in maintenance mode. Financial dimensions can’t be deactivated. Instead, they can be removed from an account structure, so that they’re no longer used by any legal entities that use that account structure.Tags can be activated or deactivated at any time.
Ability to deleteDimensions can’t be deleted if they’re referenced anywhere, such as on a posted transaction. If the dimension references an entity, the entity and entity values can’t be deleted. This restriction helps maintain referential integrity.Tags can’t be deleted. This restriction helps maintain the tag values that have been entered on posted transactions. However, tags can be deactivated at any time. If a tag references an entity for a list, then no reference to that entity is maintained. For example, if the tag is mapped to the Customer name entity, customers can be deleted, because the tag values hold no reference to the customer. In addition, if a customer name is changed, the customer name isn’t updated in the tag values.
Ability to edit after postingDimension values can’t be edited on posted transactions, because any change to the ledger account will directly affect financial statements.Tag values are used only for internal analysis and processing. Therefore, they can be added, removed, or edited on posted transactions by using the Allow edits to internal data on general ledger vouchers feature. An audit trail is maintained for all edits that are made to the tag values after posting.
Global or legal entity specific?Dimensions are set up globally, and they are “assigned” to each legal entity through the account structures. Dimensions also have legal entity overrides, so that the same dimension can be active in one legal entity but inactive in another legal entity.Tags are set up at the legal entity level. They can be shared by using the Shared data feature. The tags and custom tag values can be copied to each legal entity by using the data management entities.

Some highlights:

  1. Create financial tags and use these in the general journals, via the web interface or through the upload function.
    • Update Financial tags after posting (as needed without need for journal entries for reclass)
  2. To reduce maintenance derive Financial tags from other values like a vendor, customer, etc. either as a standalone list or created as custom list.
  3. Unlike Financial dimensions; Financial tags are not validated against such lists and do not have to be predefined prior to use on the transaction.  
  4. Voucher screen and standard reports will show financial tags.

For the future?:

  1. We can only use tags now in GL transactions not in subledgers. It will be a much stronger feature when available on purchase orders, sales orders, and inventory close/adjustments to track write-down adjustments, purchase requisitions, and other transactions.
  2. To distribute an amount across multiple tag values. For example, the GL has one transaction for an expense, but the amount needs to be distributed across multiple Financial tag values for reporting purposes.

Business Central is now the time? – ask Synergy Software Systems, Dubai.

January 25th, 2023

See a collection of features designed for a particular role, and learn how to get to other features in the application.

Dynamics 365 Business Central is an all-in-one business management application . Upgrade your legacy ERP system or accounting software to a comprehensive solution to seamlessly manage your finances, operations, sales, and customer services.

Twice a year, Microsoft releases feature updates for Dynamics 365 Business Central. The first update is in February and the second one is in October. Microsoft has named these updates as release waves – 1, 2, 3, and so on. These updates both improve BC’s features and enhance its performance, to help users be more productive and more efficient.

How to implement Business Central in my business?

It’s easy contacting us to or schedule a meeting to assess your current ERP system, and business operations, challenges and future needs to assess how well whether Business Central fits.