Upgrading from 17.208.0034 to 18.101.0039 - acumatica

I am trying to upgrade to the latest build of Acumatica 2018 R1 from the latest version/build of 2017 (with a clean Sales Demo database) and get the following error:
The database cannot be upgraded because your current build (17.208.0034) is incompatible with the build (18.101.0039) you want to install. Wait for the next update package that will be compatible with your current build.
Does anyone know which 2017 R2 builds are compatible with 2018 or is there some type of workaround or do we have to wait for another version of 2018? Thanks

I would assume update 1 for 2018R1 would work with update 7 because update 8 was just released and the code should be comparable. If you don't have a backup of update 7 for 2017R2 and ONLY if this is demo data I have in the past just reset my version number in the Versions table back to a previous version. Try to set yours back to 17.207.0029 (requires access to SQL and an update statement to the Version table)
The problem here is you don't know what kind of issues you are going to run into as you are trying an unsupported version by changing the existing version value. Make sure you test plenty before you demo if going this approach :)
Best result is to restore to a 17.207 database backup and then upgrade. I backup each version before upgrading for issues like this (local development databases).

Related

Not able to add new azure function in VSCode

I opened my project repo as usual , then I noticed that I can't add new azure function
the + icon disappeared:
I don't know how to get it back ?
After reproducing the same by downloading the latest July 2022 - version 1.70 we faced the same issue. This might be a bug that is seen in the latest release.
You can follow the updates from the tickets that I have raised over Github - Azure Functions Support.
However, as an alternative, you can install the previous stable June 2022 (version 1.69).

Azure Functions Upgrade from beta to ~2 breaking existing code

We have been using Azure Function runtime version as "beta" and Microsoft.Azure.WebJobs.Extensions.EventHubs - version 3.0.0-beta5 package to bind with Eventhubs.
Things broke down completely after azure portal started prompting for Upgrading to version 2 for Azure Functions. With or without changing the runtime to ~2 (or any specific 2.x.x.x version) it is failing.
Can someone make it clear on what needs to change if we want to target version 2? I tried to upgrade Microsoft.NET.Sdk.Functions to latest 1.0.19 and Microsoft.Azure.WebJobs.Extensions.EventHubs to latest 3.0.0-beta8. All I get is assembly loader errors!
Please help!
You can find the description of this breaking change and recommended steps in this issue.

Upgrading ExpressionEngine database with already upgraded code?

If you've upgraded and EE site locally, and committed all of the changes through i.e. GIT, how are you supposed to upgrade the database on the production environment when you pull the upgraded codebase up to production? I've tried running the installer for the version the codebase is on but none of the migrations run. It says I'm already upgraded when the database is clearly still the older version.
The version number is stored in system/expressionengine/config/config.php.
$config['app_version'] = "273";
In order for the migrations to run you have to change that version to the old version you upgraded from.

Installshield 2010 - On upgrade check its already upgraded to certain version

I'm currently updating my installer (Basic MSI) for a program to v5.00.0000. I need InstallShield to check that if it's an upgrade, it must be on at least 4.00.0034.
So if it's not previously installed, it installs ok.
If it's on 4.00.0020, it must return a message to say please upgrade to v4.00.0034 first.
Thanks,
Ian.
Examine the ISPreventDowngrades action and the major upgrade item that finds newer versions, or read up on how to prevent downgrades. You can then copy this approach, tweaking it to instead find and error out on ones less than 4.0.34.

Create Upgrade Patch For InstallShield Installer

For our latest release, we want our customers to only download an upgrade patch of our applications and instead of uninstall and re-install all the process will be done by upgrader patch but I know nothing about this even after I googled it! Where to start guys? Note that our new release includes database upgrade as well as production code!
We are using .NET 4.0, Visual Studio 2010, C# and VB.NET in our software.
I might be a bit late to the party but hopefully this post helps anybody else who is looking for this answer.
You can use the 'Patch Design' method to create patches. You can find it in Installation Designer tab under Media.
For this you will need the latest build (msi/exe) and one or more previous build(s). In 'Patch Design' add a new patch configuration. From there you can specify latest version and previous version(s) of your setup file. If you are using Express version then you will need uncompressed build for both latest and previous. If you have Professional version then it can decompress it for you.
After this, just hit Build Patch and it will create a update.exe with only differences between latest and previous builds. It is quite smart in a way where it will only add the binary differences.
Good luck.

Resources