When will the API \entity display the patch level?

Hi ​@darylbowman,

I’m not sure it’s required there. 

What do you need to know the patch # for?

Comparing build numbers is an easy way to tell if a customization ‘breaking’ can be blamed on a recent upgrade/update/patch. I know it’s on the login page, but I was trying to find a way to programmatically get the value without scraping the login page.

​@darylbowman 
Honest question though. Have you ever encountered a situation where a patch broke a customization?

Just the other day. As a result of installing patch 2 on 26.100.0175, a completely custom Modern UI screen was loading as a blank white screen until customizations were republished. I believe ​@Kyle Vanderstoep and ​@Tony Lanzer encountered the same thing.

​@darylbowman I see. Thanks for providing the details. We are aware of that and it’s fixed already. That’s an issue with the patch application process. I was asking more about the patch introducing breaking changes, though. I’m not aware of any of such issues.

I’m not aware of any either. That’s not really the point though. It could happen, and while building a process to compare major or minor build changes, it just makes sense to include patches. I’m wondering if Acumatica will include the patch version in the API or if not, why not.

​@darylbowman 

Currently we don’t have plans to include it. I guess we could, but that is a very low priority task in my opinion.