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

LS_67

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Ok I have tested your page under Beta 2.2. This is quite good, but does not resolve our problem. In attached file an extract of our Catalog. I think we will create for each category of products a simple merged file (to be updated) and the real document where to copy blocks of items coming from the merged file. Is there any way to programaticly create elements in Publisher from Text like XTags does ? http://emsoftware.com/products/emtags/ This might be another solution Catalog_extract.pdf
  2. Hi Hangman, thank you for your quick answers. I'm not actually using the Beta version, and the current version of Publisher cannot open your file. This is not really an 'issue', but I'm just searching for a solution to our needs and thought this new functionality may help. I will ask for Beta version to see what's really usage of Text variables. thanks
  3. please show to this video : https://player.vimeo.com/video/430080228 this is a complete and commercial plugin to Indesign, but it shows the link between Data and merged documents to update them. The goal is to automate, as far as we can, the creation of our catalog which has actually approx. 300 pages and create versions in other languages. But perhaps, there are actually other solutions than merge Data, as import Tags to create automatically Text boxes, picture boxes, and insert content ?
  4. Hi Hangman, as attached files a very simple example : JSON : folder for the 2 versions of my data to merge Model.afpub = model for merging data Merged1.afpub = 1st result of the merge Merged1_modified.afpub = insert a picture and put the item in a new page at end of ducument then replace the ART.json file with the JSON/b_version/ in the main folder and in Publisher reload the file. Merged2.afpub is the new result of the merging update. This will be identical to Merged1.afpub (only with new Data), but all modifications (insert picture, move item) are lost in this new document. PublisherTest.zip
  5. Hi Hangman, thanks for replying and for the video. I will try it again. What I meant was more like the VLOOKUP function in Excel, applied to a text Variable which could be an Item Nr. So, in a bloc of Text the Variable refering to an unique Item Nr (first column of the merged data file), and in other blocs field values of the found row of this item (price, description, picture Address, ... I have just to leave now, I will try to make an example and send it here
  6. Hi, I hope this is the good place to ask : should it be possible to link Item name and price to unique item number of a merge file ? Merge system in affinity is a great function, but incomplete to make catalogs for instance, because each time, a new document is created, like in Word or Libreoffice. We need a system which can update fields, for example price update with modified merge Data files. So in the Text Variable saved should be a field (ex: price column x) refering to an unique value of the column 1 (item Nr) of the merging Data file. I'm rather new with Publisher and perhaps these functionalities are available in an add-on, but I didn't find. thank you
  7. Hi Walt, I've generated a new file without the BOM and it worked well ! This should perhaps be added in the documentation. thank you for your help.
  8. Hi, I'm just new with Affinity products. I don't know if you resolved this problem, but in my case the fusion doesn't recognise JSON files. I have read this post and the documentation about the first level... My file looks like the same Walt describes, as a collection of objects, with just one level, but this is not accepted 🤔 As a feature request with this system, it would be very cool to get JSON Data as an URL (HTTP Get), so that at the refreshment of the document always take the latest version of the customer's Data to place in it. here a JSON file which gives an error on Line 1 / Char 1 If someone could explain me what's wrong in there, this will really help me. Luc data.json
×
×
  • 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.