TM1 Forum

Thanks for the reply Burnstripe! From the backup config files is appears that this parameter was always set to 0. I do not recall ever changing it but would not put money on it... What I do recall is there may have been instances where the following could have been tested: #MTFeeders=T #MTFeeders.At...

On PA 2.0.7 (11.5.00000.23) I had additional detail in my TM1Server.log file relating to feeders. On PA 2.0.9.13 I no longer get this - anyone seen this and have any ideas on what I may have tweaked to break it? IIRC, this model used persistent feeders and it is still enabled in the tm1s.cfg 20188 [...

I would suggest attributes for this as often you need prior day or prior business day.
These could be easily updated using TI and and spreadsheet send (with your workings for business/non-business days).

Have you tried FormatDate using some of the formatting mentioned here ? My guess is that it is no different to what you are getting now but worth reviewing the options. Alternatively, I think in previous cases I added the date of the first week to an assumptions cube then used that as the seed to ca...

... Hi, Thanks a lot for your inputs. Would this export and import really work ? I have seen that exporting to an Ascii takes more time compared to direct update in cubes as it need to access some shared drive path to create/update the file right. As per our data flow this source view need to be cr...

I found that using TI to copy intra-cube or inter-cube can be very slow in certain cases using a CellPutN/CellIncrementN. In one case it was taking almost 4 hours to create snapshots across a few cubes with Sales being particularly slow due to granularity and rules. Changing the process to export to...

Officially supported to Windows Server 2012 (per IBM report) but cannot see any reason why it would not run on 2019 i.e. be compatible.

Looks like I jumped the gun here and assumed the current MDX view discussion.

Does look curious - What is set in prolog for the DataSourceNameForServer etc? Need to see what is happening in prolog to build and reference the set.

Check out this thread

Maybe not the most elegant option but works with two clicks:
- Right click in the header area above the first element
- Navigate to Level options then select the highest number i.e. expand to that level for all items.

Still a bit confused with your original MDX working as you were basing a lookup to }ElementAttributes_Month using members from Month. Anyway, a few things to consider: When using ORDER, ASC and BASC are for different cases where BASC breaks down any hierarchies before sorting, ASC sorts within hiera...

Thanks Adam - will be really useful for some IT departments who want to push new versions from time to time.

My recollection may be flawed, but I thought there were some issues in dynamic reports regarding formulas that would not copied down as much as needed. IIRC, this wasn't too long ago and it could well be in the range of versions of an early 2.0.9. Does this ring a bell to someone ? Maybe worth havi...

Some other things you can try: - Right-click on the TM1RPT row cell then navigate to the Edit Set option, choose something else and see if that triggers a rebuild. - Check the TM1RPTTitle references in the TM1RPTView cell. Start by removing them all and rebuilding. If it rebuilds, add them back base...

Yes, I was a bit sneaky there and called it all MMAP throughout.

The point was for you (and others reading this) to understand the concept of the Generate() then apply it, which you did.

Generate needs two components - the first being a set to enumerate and the second being where you are doing something for each item in the first set. Essentially step 1 is to pick up MMAP with a Vintage. Step two is to convert those Vintages to members using StrToMember from the attribute string. Tr...

May be easier to if we can see an example of the two dimensions and their attributes.

Alternatively, have a look in the MDX guide in Tips and Tricks section for some ideas.
You will likely need to start with Generate()

The dash in the first screenshot is an Em Dash - MS Word is generally to blame and converts dashes to em dashes via auto correct as you type. Someone then copies these to Excel or elsewhere then into TM1 and you have an issue. Em Dash is Unicode Character “—” (U+2014) Edit: you may need to check the...

Why not create a rollup of relevant years and reference that on the left?
Children (Leaf elements) of that rollup are then used to feed to the right.

Do other dynamic array type formulas work in the Citrix environment?