Viewing 15 posts - 1 through 15 (of 17 total)
  • Author
    Posts
  • #10655
    tor2dbear
    Member

    I need support concerning the Multiple Records function (layout provided) which becomes grayed-out for som reason. I managed to achieve the exact same process before but now I can’t seem to manage. (Although it was only the sub switch under ”layout provided” that was available.)

    Problem:
    When I add an additional text frame with anchored text frames inside the MR option disappears.

    The text frame is visible in the image attached, called ”Utställare”. Without this text fram it works fine.

    <<alla>> is comprised of two data source entries and a static text.

    https://ibb.co/ckr0Ffj

     

    Help is much appreciated!

    #10656
    tor2dbear
    Member

    Just to show what I’m after and that it was possible before I’ll attach a screenshot from an earlier export:

    https://ibb.co/0qy5P3F

     

     

    #10657
    Pat
    Staff

    Hi tor2dbear and welcome to our support forum

    We received the additional data by mail and will have a look at it soon.

    Official MyDataMerge Team

    #10658
    tor2dbear
    Member

    Thanks!

    #10659
    Pat
    Staff

    We’ve investigated your case.

    Multiple records per page require the same group of content repeated all time.
    By adding a list on the right with other content “<<alla>>” you break the rule and multiple records per page gets greyed out.

    If you need that list on the right you could do the following monkey patching (and this only is worthwile if you have more than 19 records) :

    • Add “<<alla>>” to every group on the left and on the right side list remove the “<<” and “>>” from each “<<alla>>”.
      This way MyDataMerge will recognize it as correct multiple records per page. Set it up as usual.
    • Then activate the option below the multiple records per page (layout provided) – “Add tags manually”.
    • Once you export, MyDataMerge will pausee before the merge proceess and let you manually setup data merge tags in InDesign
    • In this state, remove all “<<alla>>” tags from your group (we know thats odd but that’s currently the onliest way to make it work what you need).
    • Then get the Data merge panel, highlight the first “alla” in the list on the right and click the first alla tag in the data merge panel (you will recognize there are 19 of each). Continue with each of them.
    • Once you’re done head back to MyDataMerge and press continue.

     

    I added a ticket to our developers if we can make this more comfortable

     

    Official MyDataMerge Team

    #10660
    Pat
    Staff

    I think our developer got a solution thats better.

    We’ve send you a proof of concept – we just needed to replace the fonts.

    • The basic idea is to include “<<alla>>” in the text frame of a group on the left, then make the textframe smaller so <<alla>> is cut off (overset text).
    • Now connect that frame with the one on the right, so <<alla>> is located on the right. Add that textframe to the group on the left.
    • Repeat this with all others and it should work.

     

    Minor thing: Connecting textframes doesnt work with anchored textframes.

    Official MyDataMerge Team

    #10661
    tor2dbear
    Member

    Thanks for the clarification,

    I’m afraid neither of these solutions will help me though as I have a bunch of similar files that needs to be updated in a easy manner. I will also apply skewing to the floor plan so keeping the list inside the groups will not work.

    The weird thing though is that I actually got this to work initially (Screenshot above). Unfortunately I deleted the files and started over once I saw that it was working.

    Like i wrote in my first post: The “MR per page (layout provided)” was grayed-out but “Setup additional data merge tags manually” was showing and was active. So it looked kind of like an unexpected behaviour. Although a welcomed on.

    I think in getting to this point  I removed the <<alla>> list and saved/updated it, then put it back in the Id-file and saved/updated it but I can’t seem to replicate that behaviour.

    #10662
    Pat
    Staff

    Thank you for your response.

    Indeed this sounds like an unexpected behaviour.

    I will get back to you once a Developer answers the ticket I mentioned above.

    Official MyDataMerge Team

    #10663
    tor2dbear
    Member

    Thank you

    #10664
    tor2dbear
    Member

    Okay,

    So I actually managed to replicate the behaviour when playing around with the proof of concept you sent me.

    This is what the Multiple records tab looks like: https://ibb.co/r3TLMc8

    I’ll e-mail the files (called *-test) so you can have a look. Still not sure exactly what I did. But if you can help me find that out so I’m able to use this workflow it would be much appreciated!

     

    #10665
    Pat
    Staff

    That’s great, thank you.

    We’ll investigate this and get back to you.

    Official MyDataMerge Team

    #10672
    Pat
    Staff

    We figured out the issue and fixed it for the next release.

    This fixes the unnormal behaviour but will also remove what you need. We added an “Expert mode” on our roadmap (check: https://mydatamerge.com/roadmap/). So if you want to keep this behaviour for now, do NOT update to 1.3.5.1 (will be available in the next 2 weeks).

    If you subscribe to our Newsletter (check your account settings) you will automatically be informed of new releases and features added.

    Official MyDataMerge Team

    #10673
    tor2dbear
    Member

    Okay, not the answer I was hoping for but great to hear that it’s on the roadmap. Any idea when this might arrive?

    Also, staying on the current version; do you know what exactly triggers the behavior I’m experiencing/looking for?

    Lastly, is there a difference in future between buying the software and the subscription?

     

    #10674
    Pat
    Staff

    Okay, not the answer I was hoping for but great to hear that it’s on the roadmap. Any idea when this might arrive?

    Not yet. We’re currently working hard on 1.4 release where we reorganized tons of code, added new licensing model (no changed costs), added automator interface (you can add your own automator workflows). Once that’s done we’ll get back to the planned features of the roadmap.

    Also, staying on the current version; do you know what exactly triggers the behavior I’m experiencing/looking for?

    Its a rare situation but this should do it: Add your layout witout the “<<alla>>” list. Then configure multiple records per page (layout provided) and make sure its activated. Save it as MyDataMerge project. Then add the “<<alla>>” list and update the layout in MyDataMerge. Here’s where the bug comes ins: The multiple records setting was still YES even if it was greyed out. You can still save the project as long as you don’t change multiple records option.

    With the bugfix the option is set to NO automatically if new stuff is added to the layout that doesn’t fit the rules for multiple records per page (layout provided).

    Lastly, is there a difference in future between buying the software and the subscription?

    Subscriptions will receive master updates with new features like the above mentioned automator feature or the ones on the roadmap – and will receive premium support (e.g. we also help writing custom javascripts for usage withing MyDataMerge where applicable). One time purchases will receive bugfixes but stay with the version they purchased (no master updates).

    Official MyDataMerge Team

    #10675
    tor2dbear
    Member

    Okay,

    Thank you for all the help. I’ll have to evaluate pros and cons for my particular use case right now.

    Although I must say, it’s a really nice product you got and a great addition to the underwhelmingly limited built in data merge function.

    Even if it turns out not to be our best option right now I’ll definitely be looking out for future updates and workflows were it might come in handy!

Viewing 15 posts - 1 through 15 (of 17 total)
  • The topic ‘MR layout provided grayed out’ is closed to new replies.