Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2021 Release Wave 1Discover the latest updates and new features to Dynamics 365 planned April 2021 through September 2021.
Release overview guides and videos Release Plan | Preview 2021 Release Wave 1 Timeline
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
With the upcoming release of the 2015 U.S. Year End Update for Microsoft Dynamics GP, we wanted to get all of our table and column changes in one place. If any changes are made after this is posted, we will update this blog with the cumulative changes.
Existing 2015 U.S. Year End Update Table Changes for Microsoft Dynamics GP2015 Only:
UPR10100 – New Column: W2Published
Existing 2015 U.S. Year End Update Table Changes for Microsoft Dynamics GP2013 and Microsoft Dynamics GP 2015
PM00204 – New Column: TEN99FATCAFILEREQ
BE010130 – New Column: LowestCostPremium
BE020230 – New Column: LowestCostPremium
UPR00905 – New Column: LowestCostPremium
UPR10110 – New Column: LowestCostPremium
UPR10100 – New Column: PayerKind
UPR40100 – New Column: PayerKind
Be sure to check back to the 2015 Year-End Blog Schedule page to review current and upcoming blog posts and other helpful resource links related to Year-End Closing for Dynamics GP.
Thank you! Lance Koplin | SR Support Engineer | Microsoft Dynamics GP
I also received an error on PM00204, UPR00100, UPR00905, PM40100, & SY00500.
Got around them by extracting data, resetting DU0030 status to 15 for those tables, recreating tables via maintenance--sql in gp & then re-importing old data. I did a practice run on an earlier version and did not get those errors. Funny thing though is that it only happened on one company database out of 8 companies ( the primary company in use )
I also received an error on table UPR00905 when upgrading to GP2015 with the year-end update.
I am in the middle of an upgrade and received an error on table UPR00905
I deleted the table and continued with the upgrade.
I would like to know why I received an error on this table.
Business Applications communities