Archive for March, 2018

February release update for Dynamics AX 2012 R3 CU13 – ask Synergy Software Systems

March 27th, 2018

The February release for Dynamics AX 2012 R3 version is now available in LCS on the updates tile inside your R3 project.
This update is a collection of smaller functional improvements and technical fixes.
Bugs were fixed in all areas, with enhancements found in Warehouse & Transportation, Master planning, Service Management, Procurement, Sales, Client, Server, SI, Project Accounting, Inventory, Retail, DIXF, APAC, Europe and LATAM localizations, Production, Cash and Bank, Expense, and Tax updates

This release is a cumulative package including all other fixes released in the prior CU13 update as well as the recent monthly updates.

• Primary Build: 6.3.6000.4901
• Number of Application hotfixes: 121
• Number of Binary hotfixes: 16

Details of the install process can be found here: https://technet.microsoft.com/en-us/library/hh538446.aspx#PackageR3

for more information contact Synergy Software Systems tour Dubai based Dynamics Ax partner.

#Dyn365FO Spring 18 release

March 24th, 2018

The release is due out in April and brings many new features:

Business productivity
Alerts – Client-based alert functionality enables a user to define alert rules based on business events, such as when an invoice is paid or a customer changes an address.
Optimization advisor – Uses telemetry to analyze customers’ business processes, finds optimization opportunities, uses application data to quantify the opportunities, and then recommends solutions.
Project timesheet mobile – Employees can create and submit project timesheets. The use of saved favorites and the ability to copy from a previous timesheet facilitates rapid, accurate time entry.
Edit default project fulfillment hours – Project resource managers can edit the default hours as part of the project booking fulfillment process.
Reserve project resources past the task end date – Project resource managers can fulfill resources on tasks past the current task planned end date..
Person search report – You can find a person and their personal data in Finance and Operations.
Data sharing for customer and vendor tables –share Data across customer and vendor tables and related tables across multiple legal entities.
One voucher deprecation – One voucher is turned off by default, through a General ledger parameter.

Extensibility and customization
Customizations through extensions only – Migrating customizations from one release to the next has been simplified by moving away from over-layering to the use of extensions.
Extensibility requests – Customers can submit a request to Microsoft for extension support to be added to the product for a needed scenario. The Spring ’18 release enhances this feature by moving it to Lifecycle Services.
Extensible project work breakdown structure – Enables customization of the project work breakdown structure using extensions. This replaces the hierarchical grid control used for the project work breakdown structure with a standard grid that supports hierarchical data.
Embedding PowerApps in workspaces and forms – Use PowerApps to embed data from external sources into Finance and Operations data.
Custom fields – Organizations can add custom fields to tailor their application to their business requirements, using a no-code extensibility experience.

Integration
Integration with Common Data Service (CDS)
Integration with Dynamics 365 for Field Service – Provides data integration to support scenarios where Field Service activities are done outside Finance and Operations, leveraging the data integrator.
Integration with Dynamics 365 for Project Service Automation – Supports scenarios where project and resource management activities are done outside Finance and Operations, and the project accounting activities are done in Finance and Operations, leveraging the data integrator.
Integration with Dynamics 365 for Talent (Public Preview) – Provides data integration of the appropriate HR information into Finance and Operations.

Improved support experiences
Telemetry-based KB recommendation – Telemetry from a production environment can be used to identify the application hotfixes that apply to a tenant.
• KB recommendations when entering a support case – LCS provides telemetry-driven KB recommendations.
Report production outage – Provides a quick and effective channel to escalate issues to Microsoft Support if the services in a production environment are degraded or become unavailable.

Supply chain management
Vendor collaboration – RFQ process – Enhancements make it easy to tell who entered a bid (a vendor or a procurement department).
Partial shipment of a load (split load) – Allows single loads or multiple loads to be fully or partially loaded.
Immediate replenishment of locations – Used during wave execution if allocation fails for a location directive line that has a replenishment template.
Reason codes added to warehouse counting and adjustment – Users can add a reason code when performing counts and when making an adjustment.
Batch balancing enabled for advanced warehousing processes.
Analytical workspaces with embedded Power BI for Cost management – new Cost administration and Cost analysis workspaces

Globalization
India localization – project and upgrade – Users can manage India Goods and Services Tax (GST) for the Project management and accounting module, and AX 2012 customers can upgrade to Dynamics 365 for Finance and Operations.
Enhanced configurability – New features include import and testing scenarios, and also broader support for configurability without coding.
Translation Service – In addition to supporting user interface translation, Dynamics Translation Service (DTS) now supports documentation translation in Microsoft Word and HTML formats (.docx, .html). DTS features can also be accessed directly from various development environments by using the DTS API.
• Regulatory service – configuration (available at the end of April) – Regulatory service targets a no-code programming approach, allowing users to configure electronic reporting formats or tax rules rather than write code for them in the underlying application.
Integration

Servicing, performance, and deployment
Improved delivery of platform and financial reporting updates – Enhancements to how software updates are provided, to improve deployment time and the reliability of servicing.
Upgrade automation – Upgrade automation makes major version upgrades a self-service operation for the customer, using LCS for non-production environments.
Service hardening – Added service monitoring and alerting for core business processes, and improved form load performance of the most commonly used forms.
Lifecycle Services sandbox self-service automation and RDP lockdown.
On-premises deployment updates. Much awaited!

Compliance
General Data Protection Regulation (GDPR) – Investments address the European privacy law’s requirements. Go to the Trust Center to learn more and find resources to help you comply. See our previous posts on the importance of this new legislation.
Accessibility enhancements – Go to the Trust Center to learn about industry-leading accessibility standards.

Finance Insights: Credit and collections

Credit and collections insights provides analytics that help organizations effectively manage their credit and collections processes. It provides:
• Aggregate views of credit and collections across all designated companies.
• Data broken down by company, customer group, and customer.
• Credit overview report.
• Collections report.
• Credit and collections details for a variety of dimensions.
• Predictive analytics to help identify trends.

Lots lots more : Retail, cds, flow, Power bi etc

For more information contact your Dynamics 365 Dubai partner Synergy Software Systems 009714 3365589

Dynamics Finance and Operations Enterprise- new ahshtag for easier search #Dyn365FO

March 24th, 2018

#Dyn365FO. All content on docs.microsoft.com now has the hashtag

Dynamics 365 FO Enterprise 7.3 Vendor collaboration

March 19th, 2018

With the Fall release (Version 7.3), Dynamics 365 for Finance and Operations has much more to offer to automate vendor self-service and collaboration, specifically around the vendor user and organization onboarding aspects.

This video demonstrates the process of inviting and approving new vendors in an organization using Dynamics 365 for Operations. Additionally, you will learn how to use the vendor collaboration features.

Ask Synergy Software Systems – Dubai, Dynamics partner

Dynmaics 365 Finance and Operations Enterprise 7.2 platform 12 on-premise enhancements

March 19th, 2018

The much anticipated release of on-premises deployments of Dynamics 365 for Finance and Operations, Enterprise edition 7.2 with platform update 12 includes features that will enables you to keep your on-premises deployment up-to-date at cloud speed.

Major improvements in this release include:
• Apply Microsoft-released platform and application updates, and code customizations, to your environment post-deployment through Lifecycle Services (LCS) for on-premises customers.
• Infrastructure setup automation improvements that enable much faster setup for most common topologies.
• Optionally disable experiences that depend on internet connectivity on the client machine, even when the client is connected to the internet . To enable this via a simple configuration update from the application functionality, you must download KB 4091763 from LCS.

We also expect the release 7.3 and Data import/export framework (DIXF) for recurring integration support to be released soon.

As always, there may be some changes in the release schedule.

GDPR are you ready?

March 10th, 2018

As mentioned in previous Synergy posts if your organization operates within the European Union (EU) or trades with the EU, the General Data Protection Regulation (GDPR) will affect your operations.

Only 6% of surveyed organizations say they are “completely prepared” ahead of the mandate’s May 25 effective date, according to the 2018 State of Data Governance Report.

17% of organizations believe GDPR does not affect them. Their organizations are misguided because any company in any industry is within GDPR’s reach. Even if only one EU citizen’s data is included within an organization’s database(s), compliance is mandatory.

So it’s important for organizations to understand exactly what they need to do before the deadline and the potential fines of up to €20 million or 4% of annual turnover, whichever is greater.

Personally Identifiable Information (PII)
According to the GDPR directive, personal data is any information related to a person such as: a name, a photo, an email address, bank details, updates on social networking websites, location details, medical information, or a computer IP address.

Personal data also comes in many forms and extends to the combination of different data elements that individually are not PII, but contribute to PII status when consolidated.

Active Consent, Data Processing and the Right to Be Forgotten

GDPR also strengthens the conditions for consent, which must:
– be clear and distinguishable from other matters
– and provided in an intelligible and easily accessible form,
– using clear and plain language.
– it must be as easy to withdraw consent as it is to give it.​

Data subjects also have the right to obtain confirmation as to whether their personal data is being processed, where and for what purpose. The data controller must provide a copy of the said personal data in an electronic format free of charge. This change is a dramatic shift in data transparency and consumer empowerment.

The right to be forgotten entitles the data subject to have the data controller erase his/her personal data, cease further dissemination of the data, and potentially have third parties halt processing of the data.

Documenting Compliance and Data Breaches

GDPR also looks to curb data breaches that have become more extensive and frequent in recent years. Data’s value has sky-rocketed, and data-driven businesses are major targets of cyber threats.

Organizations must:
– document what data they have,
– where it resides,
– the controls in place to protect it,
– the measures that will be taken to address mistakes/breaches.

In fact, data breach notification is mandatory within 72 hours if that breach is likely to “result in risk for the rights and freedoms of individuals.”

Data Governance and GDPR:

Data governance and GDPR go hand in hand. A strong data governance program is critical to the data visibility and categorization needed for GDPR compliance, and it will help in assessing and prioritizing data risks and enable easier verification of compliance with GDPR auditors.

Data governance enables an organization to discover, understand, govern and socialize its data assets – not just within IT but across the entire organization. Not only does it encompass data’s current iteration but also its entire lineage and connections through the data ecosystem.

Understanding data lineage is absolutely necessary in the context of GDPR. Take the right to be forgotten, for example. Such compliance requires an organization to locate all an individual’s PII and any information that can be cross-referenced with other data points to become PII.

With the right data governance approach and supporting technology, organizations can ensure GDPR compliance with their current, as-is architecture and data assets – and ensure new data sources and/or changes to the to-be architecture incorporate the appropriate controls.

Stakeholders across the enterprise need to be GDPR aware and enabled so that compliance is built in,

Microsoft public preview of Azure SQL Database Managed Instances – running SQL Server workloads in the cloud

March 10th, 2018

Microsoft released the public preview of Azure SQL Database Managed Instances – a new option for running SQL Server workloads in the cloud.

Managed Instances (or Azure SQL Database Managed Instances, are a new PaaS database offer that joins the Azure SQL Database and Elastic Pool services. Within this PaaS family, Managed Instances take care of operational aspects like ensuring: high availability, backups, and applying patches, making these simpler and less time-consuming to administer.

While many organizations have benefited from using Azure SQL Database for new applications, it has been a significant challenge to migrate existing workloads because of key functionality gaps versus on-premises SQL Server.

Managed Instances address that problem, by providing vastly improved compatibility. Organizations can therefore more easily migrate existing on-premises SQL Server workloads to the cloud while retaining many of the manageability benefits of a PaaS offering.

Managed Instances require less operational oversight compared to traditional on-premises SQL Server,. Use of the service however, doesn’t free you from the responsibility for checking availability or ensuring that security is configured appropriately. It also remains the DBA’s responsibility to optimize performance, and to handle other operational concerns like making sure jobs complete successfully, or general troubleshooting – its platform as a service. High availability, automated backups, point-in-time restore, automatic plan correction, threat detection, vulnerability assessment, and other intelligent features are built-in into service without any additional charge. OS patching and database upgrades are handled automatically and do not require any action.

In addition to built-in monitoring and maintenance features, you can use any 3rd-party tool to monitor and manage your instance, because most of the system views are exposed.

Connectivity

Azure SQL Managed Instance is not a service on public endpoint. Azure SQL Managed Instance is placed on private IP address in your VNET. It is just hosted and managed by Azure cloud.

Currently, Azure SQL Database PaaS has two main offers for the customers who use SQL Server database and want to migrate to PaaS:
1.Managed Database – isolated and self-contained database service that has database scoped functionalities.
2.Elastic pool – a group of Azure SQL databases that share the same resource.

However, current Azure SQL Database offers don’t provide entire SQL Server “Instance as a Service” as PaaS model. As a result, some of the instance-level features in Azure SQL Database PaaS such as SQL Agent or linked servers are not supported because they are not applicable on the database level.

Currently, the only way to get the full SQL Server instance in Azure is to use Azure SQL VM that handles underlying infrastructure (e.g. disks), but still not have some SQL PaaS features as Azure SQL Database.

Managed Instance is a SQL Server Instance in Azure cloud that shares the same code with the latest version of SQL Server Database Engine and has the latest features, performance improvements, and security patches. It has most of the SQL Server 2017 features (excluding some on-premise Windows features such as Windows logins or potentially harmful features such as extended stored procedures) and enables you to put almost any database that you have in on-premises SQL Server instance. Every instance is fully isolated from the other customer instance and placed in your dedicated subnet with assigned private ip addresses.

Security/Isolation. Managed Instance is a resource in your network hosted by Azure cloud. You have to create Azure VNET and a dedicated subnet where the instance should be deployed. There are networking constraints for the VNET/subnet that you should review before you create a managed instance.

There is no public IP address dedicated to the Managed Instance. Only applications in customer network can access Managed Instance. Network administrators have the full control and can configure access to Managed Instance using standard methods such as Network security Groups and firewalls.

Choose how many CPU cores to use and how much storage you need. You can create a Managed Instance with 16 cores and 500GB storage, and then increase or decrease these numbers depending on your needs. Changing CPU or storage in instance can be done via Azure portal using simple slider.

Managed Instance has split compute and storage components. There are compute nodes with 8, 16, or 24 cores, that work with database files stored on Azure Premium disk storage. Every database file is placed on separate Azure premium disk, that guarantees that database files cannot be lost. Although Managed Instance relies on Azure Premium disks, it also has separate backup mechanism that ensures that even if something would happen with the files, platform would still be able to restore files from backups.

Ax 2009 Sp1 extended support ends April 2018 ask Synergy Software Systems for advice

March 5th, 2018

REMINDER: AS detailed on the official Microsoft Lifecycle policy page, Dynamics AX 2009 SP1 will reach end of mainstream support April 10, 2018.

https://support.microsoft.com/en-us/help/4043450/products-reaching-end-of-support-for-2018

Extended support definition is found here: https://support.microsoft.com/en-us/help/14085

With the increase in malware and rapid changes in SQL IE Office and Windows the risk of compatibility is increased

More concerning is the constant malware attacks which give additional focus to unsupported applications.

This will devalue your system worth.

It may not be feasible to upgrade immediately but you should at least understand the options and have a future plan, budget and contingency.

its likely that an Ax 2009 system is running on older versions of SQL, on old hardware etc.
If an Ax 2009 system is to last you another year or so then consider some short term action to audit, patch, retune sql, clean up logs. test back up restores, recompile code, resize the database, etc is worthwhile. Performance typically degrades over time, as operations and data volumes change original configuration settings need to be retuned, old data purged, maintenance tasks run etc.

Contact us about Dynamics Ax Performance and audit review.0097143365589

SQL 2008 Extended support ends July 2019

March 4th, 2018

A remdnder that Mainstream Support for SQL Server 2008 and SQL Server 2008 R2 ended on July 8, 2014. – Support Lifecycle policy, found in http://support.microsoft.com/lifecycle.

Customers are encouraged to prepare and execute on their upgrade and/or sustained engineering plans as early as possible for these SQL versions. Remaining current on your SQL Server version ensures that your product remains supported per the Support Lifecycle policy. Additionally, your software benefits from the many enhancements, fixes, and security updates provided through the latest releases.

For both SQL Server 2008 and SQL Server 2008 R2, Microsoft will continue to provide technical support which also includes security updates during the duration of extended support. See the table below for extended support end date. Non-security hotfixes for these versions will be offered only to customers who have an Extended Hotfix Support agreement.

SQL Server 2017 Cumulative Update 4

March 4th, 2018

Last month Microsoft released SQL Server 2017 Cumulative Update 4, which is Build 14.0.3022.28.

There are 55 hotfixes in the public fix list. Run the special T-SQL script in the release notes if you are using Query Store and previously ever had SQL Server 2017 CU2 installed (and you were using Query Store on any of your databases at that time). The script will look for any plans that were forced while you were running SQL Server 2017 CU2, and if it finds any, it will unforce those and then clear those from Query Store.

There are several updates both for Columnstore indexes and for Availability Groups.

There will not be any Service Packs for SQL Server 2017, so test and deploy SQL Server 2017 Cumulative Updates as they become available.

SQL Server 2017 and later versions will no longer receive SPs
The Modern Servicing Model (MSM)

Starting from SQL Server 2017:
• SPs will no longer be available. Only Cumulative Updates (CUs) and critical updates (GDRs) will be provided.
• CUs will contain localized content if it’s necessary as what SPs have done.
• CUs will be delivered more frequently at first and then less frequently: every month for the first 12 months, and then every quarter for the final four years of the five-year mainstream lifecycle.

Note The MSM only applies to SQL Server 2017 and later versions.

Earlier versions of SQL Server are not affected by this SP policy change. Service Packs (SPs) will continue to be provided for the reminder of mainstream support for SQL Server 2014 and SQL Server 2016.