How do you reload the M3 Analytics models?

Hi, I processed the DL tables and then adjusted the inital setup workflow in Birst, and ran that, then ran the main workflow and I am still not seeing any results in my M3 Analytic tables.

Is there a step I am missing? The online documentation is a bit limiting.

Also, I'm getting this error when I try to rerun the initial load - any idea who to reset that flag?

The variable M3A_CompanyFilter could not be updated since 'requirespublish' flag is set for space CIDRA_DEV-M3AEQP-Source

Find more posts tagged with

Comments

Legacy Contributor

Hi Shirely, get a ticket logged asap, there are known issues with Analytics ETLs loading at the moment that dev are working on, the ticket that speaks to publishing is 2153208

Cheers

George

vinayak-tayshetye

Hi Shirley,

To solve the error, you will have to go to source space - modeler - relate and publish the source space manually by clicking on Yellow alert symbol on top right corner of your screen. Once publish, is complete you can run the desired workflow. If published data is not useful/bad, delete last published.

Legacy Contributor

Are all the data lake tables present in your data lake which are required for M3 Analytics.

jason-billing

Yes, all the tables are updated. I put this effort on hold - waiting for Infor to update my Analytics to 16.1.8 - once that is done I'll try the suggestions above.

jason-billing

Sorry for not responding, I didnt see the notification - I'll give this a try as soon as my environment gets updated to 16.1.8

jason-billing

Hi George, does this issue exist in 16.1.8? I tried looking up that ticket 2153208, but nothing is coming up - so I must not have access to it. I'm going to try the steps below after I get upgraded to 16.1.8

Legacy Contributor

Hello,

Do you have any answer to this issue?

I have same problem and I couldn't find anything on documentation.

Regards,

B. Silva

Pierre Nolte

Which issue? The 'requires publish' error?

For this you will need to simply process the space. You can chose any process group. It does not really matter, but I'd recommend to use one of the 900 process groups as they're pretty fast.

Or , if it's the source space, you go for the start or end process group. That's the fastest

Legacy Contributor

The solution that you offer did work. Do you what is cause this specific issue? Thanks.

Pierre Nolte

It means the space is in an in-between-state. This can happen sometimes when the repository has been copied/replicated or more often it happens when an extraction has failed. In this case the space status is not reset properly and you have to "force" it by processing/publishing, which ultimately switches the flag and ensures the repository is up-to-date.

Copyright © 2025 Infor. All rights reserved.