locked
Time Dimension Error-string not recognized as valid datetime RRS feed

  • Question

  • Hi All, Im getting this strange error while trying to save Time Dimension after making changes to it. Initially, the Time dimension was built and processed based on a table. I ran few SQL Updates(changed only data not the table design or datatypes) in management studio to modify column values, then trying to make more changes in BIDS and saving the dimension. But im not able to save,string not recognized as valid datetime Error messege is poping up everytime i try and save the dimension. Im guessing this might be something to do with Visual studio? Note: -Other dimensions in project are working fine, im able to save changes to them. -Tried removing Time dimension from project and included a older version and tried to make changes/save-dint work.. -Tried to open project in VS 2008 and made changes/save-dint work... Thanks Rakesh
    Friday, May 1, 2009 6:11 PM

Answers

All replies

  • Any suggestions Please? Atleast one might have come across this problem...
    Saturday, May 2, 2009 6:02 PM
  • What is the exact error message that you're seeing? Why would you be getting a string not recognized as a valid datetime? Is your DSV not in sync with your data source?

    Sunday, May 3, 2009 1:58 AM
  • Hi Martin,

                 The error messege that im get while trying to save changes is :string not recognized as valid datetime

    If you need, i can post the stack trace as well.

    DSV is in sync. (Will refresh it once anyways). But how does it matter if DSV is not in sync?


    Thanks for the reply!

    Cheers
    Rakesh
    Sunday, May 3, 2009 4:37 AM
  • Check the dataType of the attribute in the dimension attribute. You can remove or add the attribute else re-create the dimension in worst case 

    Thank you
    Imran Shah
    imran shah
    Sunday, May 3, 2009 5:00 AM
  • Never figured out the issue. Recreated the Dimension....
    Monday, May 4, 2009 5:14 PM
  • When you initially create an attribute, it will assume the data type of that attribute in the DSV at that point in time. If the data type of that bound column changes, this change is not automatically reflected in the Source binding of the Name (or if used, the Value) properties of that attribute. It's fairly common that this change impacts name columns where the width of the field is increased in the source and now exceeds the width bound to the name column. In this situation, you'll get similar errors when processing the dimension.

    Reconstructing the dimension isn't always a non-destructive operation. If you've designed aggregations, these will now be invalidated.

    Tuesday, May 5, 2009 2:01 AM
  • I had this problem too and solved it by removing the values in CalendarStartDate and CalendarEndDate (under TimeStructure) of the dimension properties. Then I reloaded the dimension again and it was solved.
    -
    • Proposed as answer by Erik Monchen Monday, September 7, 2009 3:13 PM
    Monday, September 7, 2009 3:13 PM
  • I had this problem too and solved it by removing the values in CalendarStartDate and CalendarEndDate (under TimeStructure) of the dimension properties. Then I reloaded the dimension again and it was solved.
    -
    Thanks so much, this solved my problem and saved tons of troubleshooting! 
    Wednesday, March 19, 2014 9:14 AM