locked
ExcelImporter Issue 1<-∞ ∞->1 RRS feed

  • Question

  • Hi

    In my SL browser client, I find that if I import files to tables with a 1->∞ relationships the import works great.

    But if I try to import to the GroupList table where the relationship is:

    StoreGroup 1->Many GroupList Many<-1 Stores

    I get this error:

    "An error occurred while running this screen.
    Error details: Exception has been thrown by a target of an invocation."

    When I click to close the screen I see:

    "Invalid operations. Dispatcher has been stopped."

    Any assistance will be appreciated.

    Thanks.


    Mark

    Monday, January 6, 2014 7:51 AM

All replies

  • Hi,

    > StoreGroup 1->Many GroupList Many<-1 Stores,  I get this error:......

    I'm not sure why this happens, perhaps you could also try the Excel Import Extension to import data into LightSwitch applications. I think it is available on your side.

    Best regards

    Angie


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, January 7, 2014 8:54 AM
  • Hi Angie

    Thanks for your response.

    My LS solution presently has v 1.1 of "Excel Importer".

    Are you suggesting I go back to v 1.0?

    Thanks for your assistance.


    Mark

    Wednesday, January 8, 2014 2:09 AM
  • Hi,

    We recieved some feedback that it does not yet support VS 2013, it's recommended to use  "Excel Importer" v 1.1.

    Best regards

    Angie


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, January 8, 2014 7:37 AM
  • Hi Angie

    Yes I am using v 1.1 but that's the version that's giving the error.

    FYI, I am using VS2013 Ultimate on Windows 8.1.

    Is there any way possible to overcome the issue that I initially raised?

    Thanks.


    Mark

    Wednesday, January 8, 2014 7:42 AM