TI Funny When Recreating a Dimension
Posted: Tue Mar 10, 2009 3:42 pm
Guys,
I came up against a funny issue yesterday. We are currently running 9.1 SP U2 and I was messing around on our 32-bit windows development server. I have an outlet diemension called taps outlet (Don't ask). On the production server this has since changed to trading outlet (Much more sensible). On the dev box I completed a save as within the dimension editor to create trading outlet based on taps outlet. This worked a treat. I then copied the production dimension control file over to development (Most up to date) and started to edit the taps outlet recreate TI process. I replaced any mention of taps outlet and even checked the generated code in the prolog, metadat and data tabs. They looked fine. I saved the process as something else and ran it. Upon checking the server it had still updated taps outlet which was strange. I of course went back and checked the whole process. It was fine so I re-ran it. It updated taps outlet again. I looked further in to it. I found that taps outlet has an alias and trading outlet did not. I changed the TI process so it created the alias instead of trying to update a current one. Low and behold it worked. While I undertstand that what I was trying to achieve shouldn't work due to the lack of an alias, but I was suprised that instead of chucking out an error it updated the dimension that old process was originally pointing too. (Even thought there was no reference to it any where in the process.)
Keep an eye for this one,
Jim.
I came up against a funny issue yesterday. We are currently running 9.1 SP U2 and I was messing around on our 32-bit windows development server. I have an outlet diemension called taps outlet (Don't ask). On the production server this has since changed to trading outlet (Much more sensible). On the dev box I completed a save as within the dimension editor to create trading outlet based on taps outlet. This worked a treat. I then copied the production dimension control file over to development (Most up to date) and started to edit the taps outlet recreate TI process. I replaced any mention of taps outlet and even checked the generated code in the prolog, metadat and data tabs. They looked fine. I saved the process as something else and ran it. Upon checking the server it had still updated taps outlet which was strange. I of course went back and checked the whole process. It was fine so I re-ran it. It updated taps outlet again. I looked further in to it. I found that taps outlet has an alias and trading outlet did not. I changed the TI process so it created the alias instead of trying to update a current one. Low and behold it worked. While I undertstand that what I was trying to achieve shouldn't work due to the lack of an alias, but I was suprised that instead of chucking out an error it updated the dimension that old process was originally pointing too. (Even thought there was no reference to it any where in the process.)
Keep an eye for this one,
Jim.