TM1 Forum

In PA, you'll find that setting in the }Capabilities cube, the specific item is "Consolidation TypeIn Spreading" and you'd want DENY for the EXECUTE permission.

What values are you passing to the 'hideForm' and 'bypassPAWchooser' arguments of LogonSSO? I use the below in a few reports for PA on cloud and it works fine. Reporting.LogonSSO(<url>, <database>, False, "") What version of Pafe are your users running and are some of them already logged i...

Double clicking a SUBNM cell to open set editor works in Pafe except when you have an "&" in the subset name. The dropdown selection feature of SUBNM cells also doesn't work when you have an "&" in the subset name.

If I had to guess, 'Parent' used to be a leaf element and someone used that rule to make it the sum of the 3 other elements. Someone else came along later (or same person got a tiny bit wiser) and decided to make 'Parent' a real consolidation with the 3 as children and then forgot to remove the orig...

Check out TM1py for generating a report of this sort of TI process metadata.

I see things that upset me in both your original and the modified snippets, but if I had to pick which one I'd rather read, I'd pick the modified. Personally, I don't add spaces around a parenthesis, but I like to see consistency no matter what a developer decides they want to do with spaces. I like...

Let's start with the alias and ignore any changes to the subset itself. Since your screenshots are architect/perspectives, here's specific instructions for updating the alias there: In server explorer of Architect/Perspectives, right-click the dimension and select "Edit Element Attributes"...

I doubt I have the technicalities right, but I've always explained it as the calc cache being invalidated from the CellPut and thus forcing the source view to be re-evaluated/recalculated when you try to read from and write to the same cube in a TI. I believe it's also particularly sensitive to MDX ...

Ceiling or Ceiling.Math in excel? If you simply want similar as RoundUP which would be similar as Ceiling.Math the below would give you similar results in tm1. ## result of ceiling will be same as Ceiling.Math(3.7) in excel: 4 ['value'] = N: 3.7; ['ceiling'] = N: ROUND(['value'] + 0.499999, 0); ## r...

Keep the report structured just as you have it, but try removing the TM1RptTitle for that specific dim from the TM1RptView definition. You don't need to specify all of the title dims in the report definition, just treat it as if you're defining it in the columns but keep it up in the title elements.

Which definition of Floor? If simply rounding down to nearest integer, INT will achieve this. ## result of floor will be same as RoundDown(3.7, 0) in excel ['value'] = N: 3.7; ['floor'] = N: INT(['value']); ## expect floor to be 3 If needing to round to the nearest multiple of a significance value, ...

At minimum, you'll need Pafe to use DefineCalc.

Yes

It would be great if I could get it to pause on the two Excel-based processes... I'm guessing the tm1 authentication piece is preventing you from calling the excel-based processes via a vbs script and running unattended? If not, you could call the vbs from a TI and simply make that part of the exec...

VS Code with the TM1 Helper extension.

cube data: PAW/Pafe/TM1py

Yes, parameter 278 in the sub file will have a 1 which dictates that the subset, despite being static, will be populated with all elements in that dimension anytime it is referenced or opened. As such, there also will be no element count parameter 270 in the .sub file or the list of static elements ...

Nice!

It is clever but is that really optimised? I'll defer to Elessar's judgement on whether or not my suggestion was the optimization they were looking for, but I do believe Max/Min functions can be quite a bit faster than IF statement processing. I'm sure I've read a comment before by lotsa saying exa...

If you want 'Element' to be of type S or C and not N, you'd first want to do a DimensionElementInsert.