Archive for the ‘Business Central’ category

Power BI autp install for TEAMS is coming.

September 17th, 2021
  • Power BI will begin automatically installing the Power BI app for Teams for users when they visit the Power BI service
  • Power BI admins can choose not to auto-install through a new Power BI tenant setting
  • The tenant setting has started to roll-out now, giving admins time to opt-out if desired.
  • The automatic installation will start to take effect in November 2021, for organizations with the setting enabled.

Auto-install for Power BI app for Microsoft Teams

When the Power BI app for Microsoft Teams is installed, users get better experiences without leaving Teams, like:

These capabilities are available once the Power BI app for Teams is installed for a user

The Install Power BI app for Microsoft Teams automatically tenant setting is added to the Power BI admin portal. Power BI admins can control the auto-install behavior. By default, the auto-install is enabled.

Power BI tenant setting that controls automatically installation of the Power BI app for Microsoft Teams for a user.

The automatic installation happens for a user under the following conditions:

  1. The Power BI app for Microsoft Teams is set to allowed in the Microsoft Teams admin portal
  2. The Power BI tenant setting Install Power BI app for Microsoft Teams automatically is enabled
  3. The user has a Microsoft Teams license
  4. The user opens the Power BI service (e.g. app.powerbi.com) in a web browser

Initially, auto-install applies to new users the first time they visit the Power BI service in a web browser. In the future, auto-install will occur for all active users of the Power BI service who meet the criteria.

When auto-install occurs, the following notification is shown in the Power BI service notification pane.

Graphical user interface, text, application Description automatically generated

Questions and Answers

What happening today?

Pre-announcing auto-install of Power BI in Teams.

Starting to roll-out a Power BI tenant admin setting which enables Power BI admins to choose to opt-out of the automatic installation behavior.

When will these changes take effect?

In November 2021, Power BI auto-install of Power BI in Teams will start rolling out.

Which users will be affected?

When the Power BI tenant setting is enabled, the Power BI app for Microsoft Teams will be installed for users who meet the criteria specified. Initially, automatic installation will apply to new users and will expand to all users who visit the Power BI service in a web browser after the initial roll-out in November 2021.

When should I use a Microsoft Teams App Setup Policy?

Microsoft Teams app setup policies allow Microsoft Teams Admins to install an app for a target set of users. Since this applies to all users in the specified group, you can ensure everyone who needs Power BI has it, even when they’re not active Power BI users. Use app setup policies to pin the Power BI app in Teams to the Microsoft Teams left rail. This additional step makes data and analytics prominently available throughout your organization..

Read more about automatic installation in the Power BI documentation

Read more about the Power BI app for Microsoft Teams

Read more about collaboration in Microsoft Teams with Power BI

Manage your inventory in Business Central – ask Synergy Software Systems

September 2nd, 2021

View Top Selling Items Aged Inventory

In the Business Central dashboard, select Aged Inventory to see what inventory items have been present for over 120 days, and to see how long each item has been in inventory..

Once you’ve gained insight into the efficiency of your inventory determine what are your best selling items. From your Business Central dashboard select Items, then select Report, then Inventory, then Inventory Statistics, and finally select Inventory – Top 10 List.

You are now looking at a report of your best selling products, to aid you in taking informed decisions for future inventory needs.

Check Inventory and Vendor Lead Time

After determining what products are selling successfully for your business and what products are having a slow turnover rate, determine the vendor lead time for these items. What is the time from when a purchase order is made to when the item is assembled and ready to be distributed to buyers. This data, will help you avoid the risk of being out of stock for your most popular items, a key source of revenue. 

Use the search function in Business Central located at the top right corner of your screen and search for Purchase Advice. This generates a report that shows both the total number of orders for your company’s items and the actual number in stock for each of these items. 

When you see an item that’s out of stock, go to your dashboard again and select Vendors. From there, select Report, then Purchase, then Vendor/Item Purchases. Now youhave access to a Vendor/Item Purchases report that will show the lead time of all vendors.

Easily Restock Items

Through just a few simple clicks, you have a better understanding of what is selling for your company, what isn’t, and the general turnaround time for all of these products. Such information is what makes Business Central so beneficial for inventory management. 

Use the insight gained on all inventory, to easily enter purchase invoices for items that are out of stock or close to being out of stock. Select Vendors from the dashboard screen to find the required vendor and then select Purchase Invoice, and enter the vendor invoice number along with the items purchased.

Once posted, the invoice is complete, and you don’t have to worry about being behind on inventory restock.

Future Inventory Stock

Leverage the information on inventory movement given to you by Business Central to predict future inventory needs. Go to your dashboard and find the Forecast application. Select the Forecast menu. Look at the Sales View and Inventory Forecast. 

The Inventory Forecast gives you visibility and insight about upcoming inventory needs using data in Business Central. It provides predictions for when certain items will be out of stock by analyzing current inventory and consumer trends for your company.

Keep your warehouse data accurate and updated in a timely manner with mobile transactions and use of rfid/barcode technology and also to undertake perpetual and annual inventor counts.

Ask us about the Tasklet mobile solution and its many new features. 0097143365589

IFRS 17 – compliance accelerator system- ask Synergy Software Systems.

September 1st, 2021

IFRS 17 is the newest IFRS standard for insurance contracts and replaces IFRS 4 on January 1st 2022. It states which insurance contracts items should by on the balance and the profit and loss account of an insurance company, how to measure these items and how to present and disclose this information.

This is a big change for insurance companies and data administration, financial presentation and actuarial calculations will need to change.

 

Why are IFRS 9 and IFRS 17 implemented together?

  • The insurance liability (IFRS 17) is always closely connected to the financial instruments (IFRS 9) within insurers.
  • When a client buys an insurance, the insurance liability is created and with the paid premiums are financial instruments bought.
  • Insurers want to reduce the volatility in their earnings and there are some choices within IFRS 9 and IFRS 17 which they can make which can impact the volatility.
  • Under IFRS 17 insurers can decide whether results of changing financial risk assumption go through OCI or through the profit and loss account.
  • Under IFRS 9 insurers can decide whether changes in equity will go through profit and loss or through OCI.

Both standards will impact earning volatility and hence balance sheet management choices are connected. Consequently, the IFRS board decided it is better that insurers are granted the option to implement both standards together.

IFRS 9 explains the classification and the measurement of financial instruments. Hence IFRS 9 helps to improve the information disclosure around financial instrument. Many perceive the information disclosure around financial instruments during the financial crisis as inaccurate for example impairments on financial instruments were taken too late and the amounts were too little.

IFRS 9 makes the classification of each financial instrument more logical and principle based. There are two questions which need to be answered for the classification:

  • Why is the company holding the asset; just for collecting the cash flows from the underlying asset, or is the asset also held for trading?
  • What kind of asset is the financial asset? Is it a derivative, an equity or a debt instrument? With the SPPI (solely payment of principal and interest) model it can be tested whether an instrument is really a debt instrument.

 The classification determines:

  • which accounting principle is used;
  • should the instrument be measured at fair value or at amortized cost
  • and whether earnings and losses should go through the profit and loss account or through the OCI (other comprehensive income) account.

IFRS 9 also includes a more dynamic credit loss model instructing when an insurer should take an impairment on financial assets. The model is forward looking thereby also expected future losses should be taken into account with the impairment.

 IFRS 9 also makes hedge accounting possibilities more rule based, thereby being in line with how risks are  managed within insurers.

Why does this matter?

There is a huge impact on insurers and a big change in the disclosure.

  • Almost all of the asset and liability side is hit by the combination of IFRS 9 and IFRS 17.
  • New concepts and terms are introduced.
  • The standards will impact the presented numbers. Under IFRS 17 the insurance liability needs to be based on updated assumptions which is not currently a requirement. .
  • More data with more granularity and more history will challenge internal data storage, reporting and IT performance.
  • Reporting timelines are shortened, which will challenge the systems, and the cooperation between different departments.
  • New components like the unbiased Cash Flows, Risk Adjustment, Discount Rate and CSM are introduced. This means the insurer needs to understand the IFRS 17 principles and decide how to implement IFRS 17. For example which measurement model to choose for an insurance product, which transition measure to user. Read here more about the IFRS 17 model, and here about the transition period.
  • In the balance and income statement, insurance liability will n be specified in a different way, the importance of gross written premiums will disappear, while equity will be impacted.
  • The presentation of the balance and P&L are also significantly affected.
  • Risk engines are needed to calculate the CSM and cope with all the different groups
  • Insurers need to disclose information bases on group of contracts.
  • A group is a managed group (often a product) of contracts which were all profitable, onerous, or may become onerous (decided at inception) with a certain inception year. Insurance companies can have hundreds of groups and IFRS 17 insists on this grouping to have more transparency as insurance companies cannot offset the result of one group to another

Synergy Software Systems has been implementing and supporting financial solutions in the insurance vertical for 25 years. If you need to rapidly implement a solution for IFRS 17 compliance that will sit alongside your existing erp and finance systems then call us on 0097143365589.

August 24th, 2021

A bungled data migration of a network drive caused the deletion of 22 terabytes of information from Dallas Police Department police force’s systems – included case files in a murder trial,during a data migration exercise carried out at the end of the 2020-21 financial year

“On August 6, 2021, the Dallas Police Department (DPD) and City of Dallas Information and Technology Services Department (ITS) informed the administration of this Office that in April 2021, the City discovered that multiple terabytes of DPD data had been deleted during a data migration of a DPD network drive,” said a statement [PDF] from the Dallas County prosecutor’s office.

14TB were recovered, presumably from backups, but “approximately 8 Terabytes remain missing and are believed to be unrecoverable.”

The Home Office initially issued a statement saying the data loss was down to a “technical issue”, which had been resolved, There must have been some technical resolution because the Home Office later said it was not a technical issue after all, and in fact a “housekeeping error” with Home Secretary Priti Patel saying: “Home Office engineers continue to work to restore data lost as a result of human error during a routine housekeeping process earlier this week.”

In a letter published by The Guardian, National Police Chiefs’ Council (NPCC) deputy chief constable Naveed Malik, lead for the organisation on the Police National Computer (PNC), said approximately 213,000 offence records, 175,000 arrest records and 15,000 person records had potentially been deleted in error. The DNA database connected to the PNC saw 26,000 records corresponding to 21,710 subjects potentially deleted in error, “including records previously marked for indefinite retention following conviction of serious offences”. The letter also said 30,000 fingerprint records and 600 subject records may have been deleted in error.

The PNC dates back to the 1970s. The current iteration is a Fujitsu BS2000/OSD SE700-30 mainframe based in a Hendon data centre, running Software AG’s natural programming language-using ADABAS database. The UK’s territorial and regional police forces, Serious Fraud Office, Security and Secret Intelligence Services (MI5, MI6), HM Revenue & Customs, and the National Crime Agency all make use of it. They have controlled and 24-hour access from remote terminals and through local police force systems.

These incidents highlight the importance of backups and backup and recovery processes. How often do you test whether you can restore your back ups? Does this still work for restoring older back ups when you upgrade? Has a move to the cloud changed the retention of your back ups, the frequency of upgrades, or the ease or time for restore?

Dynamics 365 Business Central Wave 2 release plan -ask Synergy Software Systems

August 17th, 2021

The “Wave 2” of the annual release plan for Dynamics 365 Business Central version 19 product launch is planned for October. Microsoft has publicly announced new features spanning from the platform’s expansions to new countries to new onboarding features and to the application and development features. (………. details listed here are subject to change).

 Dynamics 365 Business Central availability in new countries

 Starting from the 2021 Wave 2 release, Dynamics 365 Business Central will be available in the following new countries:

  • Argentina
  • Bulgaria
  • Chile
  • Myanmar
  • Puerto Rico
  • Slovakia
  • Ukraine

These new availabilities are achieved through partner-led localizations available on AppSource + built-in language module.

New features on the Application layer

Both Finance and Supply Chain areas will receive improvements on

. Availability of more fields on different entities for customizing pages via personalization (directly by the end-user).:

  • The availability of fields related to Vendor information’s on the Get Receipt Lines page or information related to customer’s orders on the Get Shipment Lines.
  • The Bank Accounts page now displays the Balance at Date and Balance at Date (LCY).
  • General Journals and Recurring General Journals can now display the External Document No.
  • Information about weights and volume are available in all sales documents and purchase documents (you can add the Unit Gross WeightUnit Net WeightUnit Volume, and Units per Parcel via personalization).
  • Add the Expected Receipt Date field to the Purchase QuotesPurchase Quote Archives, and Purchase Orders pages.
  • Job-related columns can be added to all purchase documents.
  • Add the Transfer Order Receipt and Shipment Quantities fields to the Item Card page.
  • Add the Description 2 field to all sales, service, purchase drafts, and posted and archived document lines.
  • Add the Source Type and Source No. fields to the General Ledger Entries page for better analysis.

Use requisition and planning worksheets to enter plans ofwhat you need to order and then create the orders for both physical inventory items and non-inventory items (such as services) to have a unified process.

Non-inventory items will support locations, and the location information will be copied in the item ledger, values, and job ledger entries records. You will be able to perform statistics for the location, also for services.

The Payment Reconciliation Journal will be improved with the following capabilities:

  • Separate number series
  • Posting preview
  • Ability to reverse the G/L register posted through the journal

The Bank Reconciliation page will be improved with the following capabilities:

  • Bank ledger entries are now filtered, so only ledger entries after the statement’s ending date are displayed.
  • When applying auto-matching, the user can decide not to overwrite any of the already matched entries or to overwrite all.
  • Many-to-1 matching is now possible, so many bank statement lines can be matched against one bank ledger entry.
  • When you transfer differences to be posted in a general journal, the entries will be auto-matched when you return to the bank reconciliation, reducing the redundant manual step.

Production processes like planning worksheets, order planning, capable-to-promise can now use information about bills of materials and routes defined in the stock-keeping units (SKU).

You will be able to specify a rounding precision for the base unit of measures to avoid rounding problems when using alternative units.

An alternative unit of measure for items can now be synched also with Dynamics 365 for Sales.

The new release will also remove the old sales documents reports (204..207) in favor of new sales document reports supporting Word Layout (1304..1307). You can ether use the new layouts (recommended) or clone the old layout to a custom layout and then continue using the cloned custom layout.

Data export to Excel. You will be able to export in excel lists embedded in a part on a page, such as Sales Lines on the Sales Order page or lists on a fact box pane. The Open in Excel action downloads a static copy of your list as an Excel file, applying your filters and sort order just as shown on the screen.

For reports, you can now select to export the report data to Excel on the request page. The Excel file will only include the raw data and not the report layout.

It will be useful for troubleshooting or data analysis. . Just go to the report’s request page and select the Send to menu. Here you have a new option now: Microsoft Excel Document (data only):

When you select this option, the report is rendered to include data only (data without the layout) and the raw dataset is presented in an Excel file. The Excel file contains the value of each field and the value of each variable and caption defined in the report. The exported dataset is the same dataset that is streamed to the reporting engine component of Business Central. When you have binary data inside the report, this is not exported into Excel (obviously) but it gives you an indication of the byte size. It works also for reportextension’s data.

Consider it as a “report inspector” for developers and consultants. Users must have the Allow Action Export Report Dataset To Excel permission assigned (you can assign the Troubleshooting Tools or Export Report Excel permission sets to them).

You can also export report data exported also as XML.

Integration with Dataverse, Dynamics 365, and Power Platform improvements

Dataverse integration. Use Integration Field Mapping to filter and choose the data to synchronize and how to couple records (this will avoid  writing extensions with custom business logic for synch).

Integration with Microsoft Teams, The Business Central web client will include a new action to share records to Microsoft Teams in the next release. This will allow you to type a message, choose recipients (team members, groups, or channels), and then send a message with a link to the Business Central record.

Power BI reports inside Business Central. In the next release, embed reports from any of your personal or shared Power BI workspaces (not only from the default workspace).

New features for IT Administrators

When using delegated admins,  create job queue entries and set those as ready to run with your delegated admin account. A licensed user from the customer can start the job queue entry to complete the process that the delegated admin created.

A partner, will be able to preload a list of recommended apps into the customer’s system (apps relevant for his business) to act as a “proxy” on AppSource. The customer can then install the preselected apps safely.

The administrator will have a new set of Automation APIs (in addition to the existing ones) that will permit the creation of user groups. New APIs for sharing files in Microsoft 365 will also be available for AL developers (these will permit sharing reports or other files using standard Microsoft 365 capabilities for cloud-based file sharing).

In the new release it is possible to use Azure Active Directory (Azure AD) groups to grant access to environments on a tenant . You will be able to associate an Azure AD group with an environment. The members of that Azure AD group will be synchronized to Dynamics 365 Business Central and granted access to that environment.

In the next release, you will be able to copy environments within and across different environment types, for example:

  • Production to Production
  • Sandbox to Sandbox
  • Sandbox to Production

Also, new log signals related to the environment’s operations will be added to the Business Central operation logs.

It will also be possible to restart an environment from the Admin Center, for example, for troubleshooting purposes.

New features for AL developers

The AL compiler will be improved. When using code analyzers, you will  receive a warning on code compilation with additional URLs for documentation that links to the possible cause of the problem and possible solutions.

Another essential and top requested feature that you will see on version 19 is the ability to perform a force-sync on per-tenant extensions.

Breaking schema changes on SaaS are never permitted, but on version 19 (under the partner’s responsibility), you will be able to make breaking schema changes on PTEs. The new force sync schema change can be triggered via the Extension Management page or directly from the tenant’s Admin Center.

Dynamics 365 Business Central 2021 Wave 2

Please always remember that with this action, you will lose any data stored in your extension.

When debugging with Visual Studio Code, you will be able to capture the execution timing part of the snapshot from snapshot debugging. Using a new (and cool!) performance profiling editor in VS Code, you will be able to investigate how your code performs.

Dynamics 365 Business Central 2021 Wave 2

An important new feature is related to control the source access of your extension’s code. A property in the app.json file called ShowMyCode when enabled, permits debugging the extension and also to download source (PTE) and view code in symbols. This is  one of the main problems with debugging. (Many partners have ShowMyCode = false in their extensions, which makes debugging the extension’s code impossibile!f.)

Plans to add new options in the app.json file like AllowDebugSourceAllowDownloadSource, or AllowSymbolsSource to protect the source access effectively. This is when writing a “work in progress” project, and some details could change.

To improve performances of the NST, in the next release, whenyou’re using OData for integrations, you will be able to specify a read-only intent to use the read-only database replica (and then offloading the production database). You will also have a limit on the number of background sessions that you can start from the AL code.

Don’t forget to check for warnings in your code NOW because some of these (marked as v15 or v16) could become errors in the v19 release