Viewing 7 posts - 16 through 22 (of 22 total)
1 2
  • Author
    Posts
  • 2022-11-17 at 1:21 pm #17523
    Pat
    Staff

    Hi Niels

    We found the issue with the columns and fixed it. It will be delivered with the next update.

    A bypass is still to have more than 1 column in the datasource. Starting a new project is a good idea.

    Additionally we can reproduce the error 404032 and are working on it.

    Pat

    Official MyDataMerge Team

    2022-11-17 at 3:21 pm #17524
    Niels Bakker
    Member

    Hi Pat,

    I think I start to understand everything and so far its working. I will def buy a full version in the next days. Thanks for all your help!

     

    Regards,

     

    Niels

    2022-11-17 at 7:35 pm #17531
    Pat
    Staff
    This reply has been marked as private.

    Official MyDataMerge Team

    2022-11-18 at 8:09 pm #17540
    Pat
    Staff

    Anything else we can help you with?

    Official MyDataMerge Team

    2022-12-08 at 5:48 pm #18116
    Pat
    Staff

    Hi Niels,

    we have implemented a fix for the invisible columns in data source selection in the upcoming update. It took longer than usual to plan this update because it’s a new master release to 2.0 with a lot of cool functions (check this: https://mydatamerge.com/changelog)

    Additionally we included an improved autolink among other stuff.

    2.0 will be released by the end of this week.

    Regards
    Pat

    Official MyDataMerge Team

    2022-12-23 at 2:54 pm #18296
    Pat
    Staff

    Is there anything else we can do for you?

    Official MyDataMerge Team

    2023-01-16 at 10:23 pm #18342
    Pat
    Staff

    Closed due to no response in a couple of weeks

    Official MyDataMerge Team

  • Author
    Posts
Viewing 7 posts - 16 through 22 (of 22 total)
1 2
  • The topic ‘Errorcode 404504’ is closed to new replies.