TM1 Forum

The main CON I've faced here - is it's inability to work with our favorite "READ on C: level" setup: it will throw error when it tries to spread forecast of consolidated element to it's children. So you need to either make users make forecasts on N: elements only, or to leave C: level to ...

Well I am beginning to wonder whether anyone out there actually uses this functionality.

Posted the same questions on a Planning Analytics LinkedIn Group at the same time - viewed by 170 people and no replies!

Morning folks! Does anyone have any actual practical experience of rolling out AI forecasting in PAW and it's limitations? I've been experimenting with it for the past half a day and I'm wondering whether it's going to be useable for our situation; The business has a cube storing KPI information and...

Thanks for the replies guys

Frustrating that PAX is now on it's 39th iteration and still somewhat buggy - here's hoping IBM get round to making it stable soon!

Hi! I haven't posted on these forums in many years and great to see that they're still going ;) Wondering if anyone can share their experience of working with PAX. We have a number of intermittent issues that I've been struggling to find a permanent resolution for. We have 3 main issues; 1 - TM1 for...

Thanks for the input guys; Had a couple more internal chats and we'll probably go down the Powershell route.

I'll post back when this is complete to advise how it went!

We're potentially embarking on a project to replace our ledger systems with a SaaS provider. Given that we'll have no access to the underlying database, data extracts will need to come via reports in CSV format. Rather than this being a manual, 2 stage, process (ie Push from SaaS, then pull into TM1...

Sounds like a plan

One option here may be to look at Replication? You could have a separate model that includes the confidential detail, then perhaps have a process which replicates across data from a summary cube?

Never - but it may help others if you say which version of the software you're running...

In

Experienced something quite similar / intermittent

Contributor subsequently removed from project for beliefs similar to declanr above

Ajay - no the new hierarchy doesn't need to be the first, and we didn't need to set anything up in the }HierarchyProperties cube

We overcame something similar in report studio by creating a parallel hierarchy in the dimension - a new parent that only has the N'level elements underneath it.

The prompt then just has a query that is set to show all descendants of.....

Re the first point;

There's really no difference between a 32bit and 64bit environment, save for the obvious which is that you'll be constrained by a maximum of 3gb in 32bit environment (with 3gb switch applied), whereas in the 64bit world you'll only be limited by the amount of memory on the server.

Or an entirely different approach - Keep journal adjustments away from TM1 entirely and have a consolidation entity in the ledger system (the data from which is loaded into TM1).

You may find this is prefered by your finance / audit team

Kugors - just one thing as mentioned above;

Are you using FEEDSTRING; or FEEDSTRINGS; ????

Just came across this box when selecting a value from a picklist - also resolved by taking auto recalc off

I have a model doing exactly (from my interpretation) what yours is trying to do Kujors. I need to feed elements in a destination cube based on text inputs (from picklist linked to target dimension) in a source cube. I found that cells were being correctly fed when data was entered in the source cub...