Skip to main content

Summary of 2022 - What All Happened this Year.

Hi Reader,

As 2022 is ending, let's review year from our prospective. While doing this review, 

I had some insights and would like to share those with my Business Central Family.


I always try to keep working towards what I hear from you and to be true this blog and YouTube channel is actually yours. Your suggestions and advice make it what it is today.

So, let's dive it in and see what all we did together in 2022.


  • Your Blog www.sauravdhyani.com with this article have a total of 1048 articles posted and out of them only 67 articles were posted in 2022.

During Covid, we started a new way to interact every weekend on Saturday. Initially few people suggested to keep that on a working day, but we all understood that workdays are busy, and we should keep it on every Saturday. 

  • #bcopendiscussion A weekly hosted meeting, by community members for community members. Thank you for your support and participation. I learned a lot in last 3 Years of hosting these Saturday meetings.



  • How I can forget about community members who are not able to join these meetings due to being on different time zones. Thank you all who watch these recordings later and correct me or suggest me stuff for future meetings.
  • Please keep suggesting content to discuss, going forward we will learn together.

With your Support following are achievements for Year 2022 - 

To align my efforts for 2023, please Vote on Poll available on Social Media Channels - 
I will make sure that I align content as per your suggestion based on Poll Results.

There were Newer Visitor in 2022 then Returning Visitors. 



Our New Initiative on YouTube is also showing some attraction with -
 

  • India had Maximum Viewer for YouTube videos in 2022.
  • It seems content is only attracting max people within age group 25-34 Years.
  • More Male Viewers. I need to work so that Female community members would engage with content. Need your advice on same.
  • And Last but important, More Non-Subscribed Viewers are watching content. The only Metrics from YouTube perspective is Subscribers, if you like the content, please Subscribe the Channel.




We could had done better but we will try our best in coming year with your support. 

Wishing everyone a Great 2023 year. Let's Learn Together and this great #msdyn365bc community even greater. Hope this year brings luck and lots of learning and growth for all of you.

Stay Connected and Keep Growing. Happy New Year 2023!

Learning is a Skill that you need to train your brain for. No one is a born genius, it's all about training your Brain. 
- Saurav Dhyani
"Sab theek hai, Aapki Duwa hai" 🙏

Regards,
Saurav Dhyani

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.