TM1 Forum

Another option for you loosely based on your first example and using INSTR:

AFAIK, they are buried in PAW some place as I asked a question about all DBs on a PAoC instance seeing them and was told that they are global within the PAW instance and not limited by DB.

For anyone looking to get some more ideas on what logging is available, please have a read through my recent blog post.

I have noticed similar behaviour when using MTFeeders=T and MTFeeders.AtStartup=T

Are you using these in your TM1s.cfg?

Unfortunately going Linux may not mean you are in the clear wrt antivirus. One of my clients had Defender running creating all sorts of havoc requiring dispensations to exclude to container folders and related programs. May be worthwhile checking what the stack would look like and if you are likely ...

Looks like something failing in the underlying MDX based on that error.
You may want to try open the board specification (Ctrl + / + q) then copy and paste into notepad and do a search to see where Label may be used.

This series may help you get familiar with some of the commands and then those concepts could be translated to Powershell.

YKud’s article may be very helpful too…

More fiddling needed - I have not had time to look at running DebugUtility 125 to clear the cache, unload certain cubes etc. before attempting a shutdown. Still not a perfect solution by any stretch but if this model and others were going to simply crash, limiting to one that may need to be killed m...

I had some time to play around a bit more with this parameter. Looks like my initial server crashes were due to too little memory on startup. Bumping this up a bit allowed the server to start as per normal. This parameter appears to be Static - no changes to it whilst running seemed to have any effe...

Without knowing what elements you actually have and are trying to derive, I was grasping. Sorry for the confusion. I have had issues with specifying the dim.hierarchy and the following may work in your case: WITH MEMBER [Period].[Period].[VAR] AS STRTOMEMBER("[Period].[" + [System Variable...

So there actually seems to be a way though not official/documented. If you add PooledMemoryMaxLimit=<threshold in MB> to your tm1s.cfg, that instance will basically just crash when the threshold is reached. Not ideal normally but may be what you need in your specific case. My TM1server.log shows the...

Do you have members that are called something like [Sep - Oct] in the Period dimension? If yes, then something like this may work: WITH MEMBER [Period].[Period].[Sep - Oct] AS STRTOMEMBER( "[Period].[" + [System Variables].([System Variables Lines].[Previous Actual Period],[Data Type].[Str...

HI Steve, Experienced the same the other day and made these notes once I noticed the problem: Over the weekend my Excel/MS 365 updated (Microsoft® Excel® for Microsoft 365 MSO (Version 2310 Build 16.0.16924.20054) 64-bit ) This morning launching the PAfE addin seems to do the necessary but no ribbon...

Paul Segal wrote: ↑Wed Oct 18, 2023 10:37 am However, the trial is somewhat limited ...

The above link had an extra close bracket preventing it from going to the intended page.
However, I think that was the old trial that has been removed.

The new PA on AWS (PA aaS) trial is here

Damn, sorry - looks like the option is no longer available in PAfE 2.0.90 - possibly added for something internal and removed.
Holding thumbs for the Idea to get further consideration...

For now you could try adding the following to your tm1features.json: Agree though that it should be a setting like it always used to be - my vote added...

In perspectives unless you are using the C API, you just use Application.Run("<macro", <par>,...) This applies to functions like ELCOMP, DBRW, DBRA etc. that you may want to use in macros. If you are using PAfE then you need to follow here: https://ibm.github.io/paxapi/#set-up But based on...

Please could you explain what you are trying to accomplish, may be easier to advise on the route to follow.

Once started up, your feeders would have fired and memory usage should be based on the data and the feeders related to them. Only when data changes would you expect more memory to be used due to additional areas being fed. "data changes" is ambiguous here as there is a concept of going fro...