Jump to content
You must now use your email address to sign in [click for more info] ×

CognitionFailure

New Members
  • Posts

    3
  • Joined

  • Last visited

  1. My concern is readability. The spreadsheet isn't only a datasource but a reference for myself as the designer of what all the values are at a glance, and having it be easy to read makes it easy to edit/update. A 70+ column spreadsheet isn't easy to read quickly, especially if I need to remember which rows I need to update for a given column whenever I change an item. However I can probably do what @lacerto suggested and have a secondary spreadsheet of items where I can make changes that will get reflected out across the entire spreadsheet. It's just a lot of upfront work. If the lookup cells for those are a single, easy to read cell then the readability problem is largely mitigated. It would be cool if Affinity had substitution logic in DMM one day though.
  2. Best to provide an illustrative example, see pics. Because each row corresponds to a single 'person' page, I don't think it is as simple as making item columns because each 'item' has its own information as well. Thanks for the idea - I think this could work, but the spreadsheet would be quite massive. Each person would end up having an additional 56 columns. The spreadsheet could have a number of dropdown/lookup style cells which could macro in the relevant columns from a different table. It wouldn't be clean to look at or design but it would take place in a single step as far as affinity is concerned. example item:
  3. I'm looking at using Publisher with Data merge in order to make my content and I'm running into a bit of a roadblock with my conceptual understanding of how it works for my context. I have two types of entities, lets say people and items. There will be a data file for each, say people.csv and items.csv. Each record in people.csv will correspond to a single page, so that is easy enough and works very well with the data merge manager (can we call it DMM?). The hard part is that each person can have multiple different items. Ideally I could define all of my items once in items.csv, and specify for each person record which items it has, ie person A has items X,Y,Z. Person B has items W and Z, etc. I'm stuck on how to use DMM to do this. My best guess right now is doing a two step process of making another document that is purely items. I would use DMM here to generate docs which I would then export. I could then specify in the 'people' csv which item images to merge into each person record. The items could be formatted like table rows. Is there a better way of doing something like this?
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.