XDI and DIM

[Jessy]

Hi everybody,

I am using Dimension Worksheet to create a dimension in TM1 9.4.1 and have successfully created one.
After I update the dimension with dimension editor, a messagebox window is supposed to appear, indicating that the xdi file will be modified accordingly. To my disappointment, I didn't receive any message.
Any ideas for this?
Thanks in advance and best regards!

[jim wood]

I'd stick with just using the XDI. The less you rely on "Features" the better in my experience.

[Steve Vincent]

Don't be so cynical

Jessy, all you need to do is open server explorer, go to file - options and change the "Local Server Database Directory" to the file path where your XDI is saved. It will then ask you to refresh the XDI if you ever save the dim via server explorer. I use this quite a lot when i want to copy a dim from one server to another without the hassle of shutting them down and copying .dim files about

[Jessy]

Don't be so cynical

Jessy, all you need to do is open server explorer, go to file - options and change the "Local Server Database Directory" to the file path where your XDI is saved. It will then ask you to refresh the XDI if you ever save the dim via server explorer. I use this quite a lot when i want to copy a dim from one server to another without the hassle of shutting them down and copying .dim files about

First of all , Thank you for your timely reply.
In fact, the XDI file is saved in the directory of the first local server database directory, i.e. that's where my local server resides in.

Another thing for reference is that, the xdi function(I mean messagebox window when updating and saving a dimension in dimension editor) works well in TM1 9.0 sp2, maybe 'cause local server executes in In-Process mode? I'm not sure

[lotsaram]

I'd stick with just using the XDI

Seconded.

Either use an XDI to maintain a dimension manually or use the dimension editor but never use both, otherwise something is bound to get out of sync.

XDIs have 4 significant benefits over dimension editor (there are more but this is what came immediately to mind)
- the ability to control element indexing with precision
- easy to cut/copy/paste/insert to create and rearrange hierarchies (drag and drop in dimension editor is very fiddly and requires the fine motor control of a neurosurgeon)
- the ability to add comments, attributes, etc. in columns D and beyond and use Excel formatting
- the ability to create elements via Excel formulas (when the dimension compiles TM1 only cares about the text value of each cell)

If an XDI maintained dimension is edited in the dimension editor, sure it will be updated if the user responds yes to the prompt, if by "updated" you mean blown away with a fresh, plain text XDI.

You can see where my allegiances lie. I'm sure any number of old-schoolers can add to the list of advantages of XDIs over the dimension editor.

The "local server directory" is where TM1 Perspectives looks for XDI and XRU files. You don't have to be running local server at all. It is better practice to have XDI and XRU files in a separate directory to the database directory as this avoids the need to share the database directory which is a huge, huge NO NO.

[Martin Ryan]

I'd stick with just using the XDI

Seconded.

Thirded. I'd never use the Dimension editor for anything more than a five element dimension. It's too easy to damage the dimension and as lotsa notes you have so much more control and functionality using and xdi file. Once you're used to it, it's also much faster.

Martin

[Jessy]

I'd stick with just using the XDI

Seconded.

......
If an XDI maintained dimension is edited in the dimension editor, sure it will be updated if the user responds yes to the prompt, if by "updated" you mean blown away with a fresh, plain text XDI.

...
The "local server directory" is where TM1 Perspectives looks for XDI and XRU files. You don't have to be running local server at all. It is better practice to have XDI and XRU files in a separate directory to the database directory as this avoids the need to share the database directory which is a huge, huge NO NO.

Hi, lotsaram

I was supposed to see the prompt, but I've never seen it in 9.4.1.
This makes me frustrated

[Alan Kirk]

I'd stick with just using the XDI

Seconded.

......
If an XDI maintained dimension is edited in the dimension editor, sure it will be updated if the user responds yes to the prompt, if by "updated" you mean blown away with a fresh, plain text XDI.

...
The "local server directory" is where TM1 Perspectives looks for XDI and XRU files. You don't have to be running local server at all. It is better practice to have XDI and XRU files in a separate directory to the database directory as this avoids the need to share the database directory which is a huge, huge NO NO.

Hi, lotsaram

I was supposed to see the prompt, but I've never seen it in 9.4.1.
This makes me frustrated

First, I'd have to say that I agree with the advice that you've been given; choose one method of updating a dimension and stick to it, otherwise there will be tears before tea time. Or at least on the first occasion that you save an out of date .xdi.

But second, I think you may have found a bug in 9.4.1.

I have only one test environment running 9.4 at the moment, which I ran some tests on last night. My initial thought was that you had the .xdi in the wrong directory but wrong directory, right directory, whatever... I couldn't get the prompt to show either.

I was going to take a further poke around later, but at this stage it does look to me like something broke between 9.1.4 (where it does work) and 9.4.1 (where, thus far, I haven't been able to get it to work either).

[Jessy]

It's very kind of you all

First, I'd have to say that I agree with the advice that you've been given; choose one method of updating a dimension and stick to it, otherwise there will be tears before tea time. Or at least on the first occasion that you save an out of date .xdi.

Yes, from my perspective, I will stick to using dimension editor. But the end users prefer dimension worksheet. We are making effors to meet their requirements.

But second, I think you may have found a bug in 9.4.1.

I agree with you. And the guide documents are not so reliable

I have only one test environment running 9.4 at the moment, which I ran some tests on last night. My initial thought was that you had the .xdi in the wrong directory but wrong directory, right directory, whatever... I couldn't get the prompt to show either.

I was going to take a further poke around later, but at this stage it does look to me like something broke between 9.1.4 (where it does work) and 9.4.1 (where, thus far, I haven't been able to get it to work either).

So is the difference between 9.0 sp2 and 9.4.1

[Steve Vincent]

But second, I think you may have found a bug in 9.4.1.

I have only one test environment running 9.4 at the moment, which I ran some tests on last night. My initial thought was that you had the .xdi in the wrong directory but wrong directory, right directory, whatever... I couldn't get the prompt to show either.

I was going to take a further poke around later, but at this stage it does look to me like something broke between 9.1.4 (where it does work) and 9.4.1 (where, thus far, I haven't been able to get it to work either).

Nuts. Remind me to test that in 3 months time as unlike everyone else we do use both, but strictly controlled and only to copy a dim elsewhere, not to maintain the dim on the same server.