This article is contributed. See the original author and article here.
Microsoft has separated all Czech-specific functionalities into distinct applications as part of the delocalization process of the Czech version of Dynamics 365 Business Central. The process intended to pave the way for the seamless integration of Czech local functionalities on top of the Worldwide (W1) version of the Business Central.
Technical Overview
Business Central has been undergoing major changes over the past few years and one of the strategy areas is application modularization, that includes localization layers. This led to critical changes in the Czech localization layer, which has now been converted into a suite of distinct localization apps. The suite contains the following apps: Core Pack, Advance Pack, Banking documents, Cash Desk, Compensation, Advance Payments, and Fixed Assets.
To ensure that both old and new Czech functionalities work in parallel in that transition period. Microsoft made sure that the old code integrated into the Base Application was gradually cleaned up. The last step is to remove Czech specific fields from the Czech Base Application.
In the next major release of Business Central 2023 wave 2 (version 23), the following Czech-specific fields will be removed from the tables, while primary keys will be updated:
Table 1251 “Text-to-Account Mapping”, field 11700 Text-to-Account Mapping Code: Code[10]
Action Required: Upgrade to Business Central 2023 Release Wave 2
To ensure a successful upgrade to Business Central 2023 release wave 2 (version 23) Czech, perform a forced synchronization of the database schema. Microsoft will ensure a seamless upgrade process for users of the online version of Business Central. However, for those upgrading to this version using Business Central on-premises, it is necessary to set the “schemaUpdateMode” parameter in CZ Base Application to “ForceSync” to synchronize the data model.
Users who are upgrading to the on-premises version of Business Central 2023 release wave 2 (version 23) Czech and higher must verify that there are no duplicate records in both tables 1251 “Text to Account Mapping” and 1252 “Bank Payment Application Rule” after the Czech fields have been removed from the primary key. This can be accomplished either by manually deleting the data or by upgrading to any version of BC 22.x where data modifications will be included as part of the upgrade procedures. It is highly recommended to back up the data in these tables before proceeding.
Summary
Czech-specific fields that were previously part of the primary key in Table 1251 “Text to Account Mapping,” specifically Field 11700 “Text-to-Account Mapping Code,” and in Table 1252 “Bank Payment Application Rule,” “Bank Payment Application Rule Code,” will be removed in this new version.
“Although it is a beginner-level document provided by Microsoft, it is difficult for all beginners to read such documents. Therefore, as someone who is also learning C# for the first time, I have organized the contents of this document into a video. I hope that beginner C# learners can learn C# more easily and enjoyably, and I want to share this content with many people.”
(In Korean, MS에서 제공하는 초급자 문서이지만, 모든 초급자는 이러한 문서 조차 읽기 어렵습니다. 그래서 저도 C#을 처음 배운다는 입장에서 해당 문서의 내용을 영상으로 정리하였습니다. C# 초급 입문자가 조금 더 쉽고, 즐겁게 C#을 배울 수 있기를 희망하며 이 컨텐츠를 많은 사람들에게 알리고자 합니다.)
“If we develop our own application that maintains unique usernames and passwords, the administrative burden becomes significant when adding or removing users across multiple applications. We also have to handle situations where a user forgets their email address. Alternatively, we can delegate this responsibility to a centralized ID provider, but many ID providers are very expensive. However, Microsoft’s authentication and authorization system is very affordable and easy to implement. Therefore, it’s content that many people should be aware of.”
(In Japanese, 独自のユーザー名とパスワードの情報を保持するアプリケーションを自分たちで開発した場合、複数のアプリケーションにまたがってユーザーを追加・削除するときに管理上の負担が大きくなります。またメールアドレスをユーザーが忘れた場合の対処も自分たちでしなくてはなりません。代わりにその責任を一元化された ID プロバイダーに委任できますが、多くの ID プロバイダーは非常に高額です。しかし、Microsoft の認証認可システムは非常に安価であり、簡単に実装もできます。そのため、多くの人に知ってもらいたいコンテンツです。)
Yutaro Tamai, Enterprise Mobility, Windows and Devices MVP, Japan
“In this eta, managing Windows devices is required for cloud-native management approach. This is good content to learn about device setup through Windows Autopilot. Why not start by getting familiar with Windows Autopilot and deepening your understanding of the latest device setup methods?”
(In Japanese: Windows デバイスの管理もクラウド ネイティブの管理手法が求められる時代です。その中で、Windows Autopilot によるデバイス セットアップの手法を学ぶに良いコンテンツです。まずは、Windows Autopilot に触れ、最新のデバイス セットアップの手法に理解を深めてみませんか。)
This article is contributed. See the original author and article here.
We are honored to announce that Gartner® has recognized Microsoft as a Leader in the 2023 Gartner® Magic Quadrant™ for Unified Communications as a Service (UCaaS)—this is the fifth consecutive year we’ve received this recognition.
This article is contributed. See the original author and article here.
Greetings, Azure enthusiasts and PostgreSQL pros! As November draws to a close, we’re excited to unveil the latest enhancements to Azure Database for PostgreSQL Flexible Server. This month, we’ve rolled out a suite of features that bolster your database’s security, optimize storage scalability, and streamline the migration process, among other improvements. Join us as we delve into these November highlights that are set to elevate your Azure PostgreSQL experience.
Feature Highlights of the Month:
Server Logs for Azure PostgreSQL Flexible Server.
Support for TLS Version 1.3 – Enhanced Connectivity Security.
Introducing Pre-Migration Validations for Single Server to Flexible Server Migration Tool.
Enhanced User and Role Migration Capabilities in Azure Postgres Flexible Server.
Microsoft Defender support **
Server Logs for Azure PostgreSQL Flexible Server
In the November update, we have introduced a significant enhancement to the Server Logs feature for Azure Database for PostgreSQL – Flexible Server. This feature is crucial for monitoring, troubleshooting, and gaining detailed insights into your server activities. Key aspects of this updated feature include:
Easy Enablement: Initially disabled by default, you can now easily enable / disable server logs through the Azure portal.
Customizable Retention Period: Configure the retention period for your logs, with options ranging from 1 to 7 days.
Convenient Log Access and Download: Once enabled and logs are generated, they can be readily accessed and downloaded from the Azure portal or via Azure CLI (command-line interfaces), providing a straightforward way to analyze server activities.
Support for TLS Version 1.3 – Enhanced Connectivity Security
This November, we’re excited to announce the support for TLS version 1.3, the most secure and current version of the TLS protocol, for Azure Database for PostgreSQL – Flexible Server. This update is crucial in strengthening the security of client-server communications. Here’s what this enhancement entails:
Advanced Security Protocol: By setting `ssl_min_protocol_version` to 1.3, Azure Database for PostgreSQL – Flexible Server now mandates the use of TLS 1.3 for all client connections. This ensures that the data transmitted between clients and the server is protected using the latest and most secure encryption standards.
Improved Connection Security: TLS 1.3 not only offers enhanced security but also provides improved performance during the encryption process, making your database interactions both safer and more efficient.
With the support for TLS version 1.3, Azure Database for PostgreSQL – Flexible Server takes a significant leap forward in ensuring the highest standards of security and reliability for your database communications. For more details on this feature, please refer Azure PostgreSQL TLS versions.
Introducing Pre-Migration Validations for Single Server to Flexible Server Migration Tool
Single to Flexible server migration just got easier! We are excited to introduce the Pre-Migration Validation feature for the Single Server to Flexible Server Migration tool. After a thorough analysis of past migrations, the team identified that a considerable number of attempts faced setup-related hurdles. To tackle this, Pre-Migration Validation has been crafted to thoroughly check the readiness of both your source and target servers. The process is neatly integrated into the Azure Portal experience, offering you flexibility to:
Validate – Examines server and database preparedness for the migration.
Migrate – Proceeds directly to migration without prior validations.
Validate and Migrate – Combines both steps, triggering migration only if validation passes without critical issues.
Each rule within the validation set is designed to return a status of ‘Succeeded’, ‘Failed’, or ‘Warning’, providing clear indicators of your migration path and any obstacles that may need your attention. This feature not only enhances the predictability of migrations but also significantly reduces stress by preemptively addressing potential issues. We are committed to evolving this tool, with more comprehensive validation rules in the pipeline to ensure your databases are primed for migration. For a deep dive into Pre-Migration Validations and to get started, explore our detailed documentation Pre-Migration Validations.
Enhanced User and Role Migration Capabilities in Azure Postgres Flexible Server
We’ve further upgraded the Azure Postgres Flexible Server Migration tool by adding the ability to automatically migrate users, roles, permissions, and ownerships from a Single Server to Flexible Server. Post successful migration you will observe the following:
All users/roles from your source server have been copied to the target server.
Database ownership and its associated objects are consistently maintained between the source and target servers.
Permissions, including GRANT/REVOKE, on all database objects are identical on the target server compared to the source server.
This new feature underscores our commitment to making the transition to Flexible Server as seamless and accurate as possible. To make the most of these features, please refer to our customer guide.
Microsoft Defender support
In our ongoing effort to enhance database security, we are proud to introduce Microsoft Defender for Cloud support for Azure Database for PostgreSQL Flexible Server. This new feature brings a robust layer of security to your database operations:
Proactive Anomaly Detection: It actively monitors unusual access and query patterns, helping to identify potential security threats before they escalate.
Real-Time Security Alerts: On detecting any anomalous activities, the system generates comprehensive alerts. These are accessible through Defender for Cloud’s security alerts page and provide essential details about the detected threats.
Guided Resolution Steps: Each alert is accompanied by recommended actions for investigating and mitigating the threat, thereby enabling quick and effective resolution.
Integration with Microsoft Sentinel: For deeper security analysis, the feature offers seamless integration with Microsoft Sentinel, expanding your capabilities for managing database security.
This feature represents a significant step forward in safeguarding your databases against evolving cyber threats and ensuring a secure environment for your critical data on Azure.
** this feature is scheduled to be available in December.
Ignite Feature Spotlight: Azure Database for PostgreSQL Flexible Server Enhancements
This November, Microsoft Ignite unveiled several exciting enhancements to Azure Database for PostgreSQL Flexible Server, solidifying its position as an enterprise-ready, fully managed PostgreSQL service. Here is a snapshot of the key features announced:
Postgres 16 Support: Now generally available, Flexible Server supports PostgreSQL 16, providing users with the latest database features and improvements. Learn more about Postgres 16 in Flexible Server.
Near-Zero Downtime Scaling: Scale your compute and storage resources with less than 30 seconds of downtime, enabling more dynamic adjustment to workload demands. Discover Near Zero Downtime Scaling.
pgvector 0.5.1 Support: General availability of pgvector 0.5.1 allows for storing AI-generated embeddings and performing similarity searches, enhancing AI (ARTIFICIAL INTELLIGENCE) capabilities within the database. Explore pgvector in Azure Database for PostgreSQL.
New Extensions – azure_storage & tds_fdw: Load and export data between Azure storage and PostgreSQL with the azure_storage extension. Access Microsoft SQL data seamlessly within PostgreSQL using tds_fdw. Learn about Postgres extension support.
Premium SSD (solid state hard drives) v2: A new storage offering supporting up to 80K IOPS (input/output per second) and 64 TB storage capacity, adjustable to workload requirements. Introducing Premium SSD v2.
Azure_AI Extension: Integrate Azure OpenAI directly with PostgreSQL for AI-powered app development using simple SQL. Read Integration with Azure OpenAI.
Private Link: Enhance security with Private Link, allowing private network database connections without exposure to the public internet. Using Private Link with Flexible Server.
Multi-Region Disaster Recovery (GeoDR): Achieve high availability and disaster recovery with GeoDR, allowing failover across regions under a single virtual endpoint. Introducing Multi-Region Disaster Recovery.
IOPS Separation for Premium SSD v1: Tailor your storage configuration to your workload’s specific IOPS and size requirements. Read Storage IOPS Separation.
Long-Term Backup Retention: Meet compliance standards and bolster disaster recovery strategies with backup retention for up to 10 years. Explore Long-term backup retention details.
As we wrap up this November recap, we also find ourselves reflecting on the incredible journey throughout 2023. It’s been a year filled with substantial growth, innovation, and community engagement in the realm of Azure Database for PostgreSQL Flexible Server. Each update and enhancement we’ve shared today not only marks the progress of this month but also contributes to the cumulative advancements we’ve achieved this year.
As the holiday season approaches, we want to take a moment to express our deepest gratitude for your ongoing support and engagement. Your feedback and involvement have been instrumental in shaping the evolution of our services. On behalf of the entire Azure Postgres Team, we wish you a joyful and safe holiday season.
Happy holidays, and here’s to a new year filled with more success and breakthroughs! Stay connected with us and keep an eye on this space for more updates. We cherish your thoughts and experiences, so please don’t hesitate to share them in the comments below. Your insights are invaluable to us.
Recent Comments