TM1 Forum

Morning all, hope you've had a great weekend.

This is my first post on here but I have used the site for many useful tips and tricks for a good while now. If some of you could spare a few moments of your time I'd be very grateful.

I've created a cube to purely capture text based comments. Alongside the common model dimensions this cube contains a 'Slot' dimension which has 10 elements contained within it (1-10) and this provides 10 rows of entry within a websheet against a number text based 'measure' elements. An example of these are:

Description
Status (Picklist from a subset)

Is it possible to send back today's date to a new element in the 'measure' dimension called 'Last Updated' when the data contained within the description field has been changed within the websheet on a row by row basis? So if a user edits the description on the 'Slot 1' dimension the 'Last Updated' date would contain todays date and the other slots would remain unaffected unless edited.

Many thanks in advance.

TM1 is not an event driven type system. When you have a websheet, all full of DBS and/or DBR(W) formulas they all update simultaneously. The only way to manage events would be to do everything via TI's, with an action button on the websheet that passes the values to be updated to the TI as parameters, not using DBS or DBR's. I wouldn't even attempt this.

I think you could do it if using an DBRW to retrieve the current description and a entry field (without TM1 formula) to enter new value combined with DBSS to send new description (with conditional logic to only update if entry field is not blank but I hope this would be obvious) and an additional DBS to send in timestamp and user committing the change if current value in DBRW is different from the data field entry value.

However when using TM1 Web my advice would also be that using DBS(W) and DBSS is not a good idea or great design and TM1 Web solutions are best managed with pure DBRW for entering or pasting data entry into.

Like tomok I think an event driven description change form with an action button would be the way to go. The action button would run a process that would both update the description and log to the same or another cube who made the change and when. This would also have the advantage of meaning you could limit user access to the cube holding descriptions to read only and so prevent the potential for users to accidentally change or delete a description. If you wanted to stick with write access to the cube another option would be to keep the "plain vanilla" slice form and do a nightly TI trawl through the tm1s log and find records for the cube where description measure is changed and write the user and timestamp to another logging cube.

Hi Both,

Thanks for your input.

Lotsaram before your reply I had went down the route of DBSS-ing the date Excel serial date minus 21,915 from excel. This is populated from an Action Button on the websheet. This allows me to compare the Serial date within TM1 to calculate the number of days since it was last updated. Like you say it's not great but it achieves the desired result.

Thanks