Overview:

Almost every customer should be set to V1, not the customer V2 method.

The issue here does not affect PMs generated using MCe Automations.

MC has had a PM generator for many years. Several versions/years back, they wrote a second version that acts differently from the first version. Somewhere around 2020 we were told by senior Accruent technician that most customers should be using the version 1 PM generator, that the version 2 was written for a specific customer and wasn't very useful for most customers.

However, the default on new installations is to be Version 2. We have tried with all customers we work with to set it to use the V1 PM generator. If you have set up your own system, you might not have done this.

What is your current value?

First step if you are having issues with your PM generations is to see what the value is currently in your system:

Select top 1 * from MCINI WHERE INI_KEY = 'WOGenerate'

So that you know if the next step is going to make any difference.

Setting it to V1

 update MCINI set INI_Value = 'V1' where INI_KEY = 'WOGenerate'

Then as good protocol, run the Select check again to verify it was set to V1.

Now your PMs should be generating in the way most people find best.

We don't support V2

If you set it to V2, and you are welcome to if you want (want to try) ... we do not support it since it was custom for one customer and since so far, of about 50 of our customers who tried it (accidentally), exactly zero liked it. So after the 1st 2 years we gave up trying to understand how it works.

A better alternative, where you have more control over the actions, try the MCe PM in MCe Automations, or try the MCe events and actions. These give you much finer control, and you can run both Accruent MC PMs and MCe Automations and MCe events and actions beside each other, so you don't have to convert all your PMs from Accruent MC to MCe if you just have one that isn't working the way you want. For more info see: MCe Automations vs MC PMs