Conditions quandry
Posted: Mon Nov 19, 2018 10:44 pm
I've conditionalized myself into a corner and I'm not sure how to get out of it.
I have two separate Flare projects (A and B - these are for separate yet related products). Most of the content from Project A needs to be used as an entire section in Project B. So what I've been doing is tagging the content in Project A with a condition, and then I created an Import file in Project B to bring in all of the content with that condition. It is working perfectly.
Now, I've discovered that there are bits of the imported content (sometimes just a few words in a topic, possibly a paragraph) that refer to yet another product and should NOT appear in the output for Project B. So I created another condition tag and tried to exclude that new condition in a target. It doesn't work as I had hoped, since I forgot that the entire topic is included due to the condition tag that I used for the import. As far as I can tell so far, there are approximately 10 topics where this is an issue (at least, that's how many I've discovered so far).
I'm thinking that the only way around this is (in Project A) to remove the condition tag for the importing and (in the import file in Project B) to specifically list those 10 or so topics. Does anyone have any other, more automated ideas? UPDATE: I just tried this and it doesn't work. If I use a condition tag in the import file, Flare ignores anything that isn't tagged with that specific condition.
In case you are wondering, I haven't combined the two Flare projects because they both need to be translated, but are developed by different teams and are on different release cycles. It is less confusing this way for our translators.
Thanks for any help!
I have two separate Flare projects (A and B - these are for separate yet related products). Most of the content from Project A needs to be used as an entire section in Project B. So what I've been doing is tagging the content in Project A with a condition, and then I created an Import file in Project B to bring in all of the content with that condition. It is working perfectly.
Now, I've discovered that there are bits of the imported content (sometimes just a few words in a topic, possibly a paragraph) that refer to yet another product and should NOT appear in the output for Project B. So I created another condition tag and tried to exclude that new condition in a target. It doesn't work as I had hoped, since I forgot that the entire topic is included due to the condition tag that I used for the import. As far as I can tell so far, there are approximately 10 topics where this is an issue (at least, that's how many I've discovered so far).
I'm thinking that the only way around this is (in Project A) to remove the condition tag for the importing and (in the import file in Project B) to specifically list those 10 or so topics. Does anyone have any other, more automated ideas? UPDATE: I just tried this and it doesn't work. If I use a condition tag in the import file, Flare ignores anything that isn't tagged with that specific condition.
In case you are wondering, I haven't combined the two Flare projects because they both need to be translated, but are developed by different teams and are on different release cycles. It is less confusing this way for our translators.
Thanks for any help!