Cross-references referencing two different elements...

Is there any way a cross-reference can reference two element tags at the same time? My attributes for my xref tag calls for two reference ID tags, but when I used the Special>Cross-references menu, I am only allowed to choose one or the other... When I try and type in the UniqueID for the other one, it telle me to use the Special>cross-references menu to chose the ID... I thought that you can type the plain ID number in the attribute value to refer to...? Thanks.
Ashley

Ashley,
It seems a little unusual that you would want to do this in the first place. How can a link have two targets? You can only go one place at a time.
Russ

Similar Messages

Cross-references in a different document

We have used FrameMaker for years (currently Version 7.1). We are in the process of switching to InDesign (CS5).
One current project is a print catalog where I put each section in a different document. One of the sections is a list of book titles. Another section is an index of authors and books by each author, with a page number cross-referencing each title with its entry in the title section.
In FrameMaker, when I open the author document, I can update all the references at once by pointing to the title document.
I don't see an easy way to do this in InDesign. Is it possible to update all cross-references at once?
Furthermore, in researching the problem on the Internet, I came across multiple comments that suggested that it's not a good idea to use cross-references across multiple documents in InDesign. Is this true, or was it only a problem in previous versions of InDesign?
Thanks for the help!

I think you should head over to the scripting forum and ask over there. Dave Saunders has just finished a huge project with thousnads of cross-refs to external docs and he might have some scripting ideas that would help you.

How to display no data found for two different elements

i wanted to display report either by dept wise or supplier wise
so when I dont have deptno related data
It should say no data found
for that I'm using if condition
same for supplier too
instead of giving twice can I give it in the same if condition
if so how

Use logical operator 'or'
like <?if:not(DEPT_GRP) or not(SUPPLIER_GRP)?>No data Found<?end if?>

Cross-references in HTMLHelp

I currently have a help project which includes popup help
topics for a large number of fields in a software suite. They are
formatted as follows:
Field Name
Field Description
I also have a number of help topics that act as summaries for
sections of the software. They include field listings (using
tables) that are formatted as follows:
|
Field Name | Field Description |
|
Field Name | Field Description |
|
Field Name | Field Description |
Each field can be referenced in several different summary
pages.
Periodically, I have to update many of the field
descriptions. Is there a way for me to automatically fill in the
field descriptions in the tables, in HTML help, so that they
automatically update when I modify the descriptions in the popup
topics? The current project is in WinHelp - I am using bookmarks
and cross-references in Word to achieve this, but we're switching
over to HTML help and I haven't been able to find a way to do it
there.
Any ideas?
- Brian

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Display cross-references' linked documents filename in the xref panel

Our company creates technical manuals consisting of five chapters, all named the same, except with a different prefix. For example the "ABC Widget" manual has an introduction chapter named "ABC 1 - Introduction", a safety chapter named "ABC 2 - Safety", etc. Many times I re-use documents for creating subsequent manuals using the "Save As" command. So the "ABC 1 - Introduction" chapter would be saved as "EFG 1 - Introduction" for the "EFG Widget" book. For all the internal xrefs it saves a whole lot of time since all of the xrefs are preserved. But for cross-document references it creates a problem. For example, if the "ABC 1 - Introduction" chapter has a xref to "ABC 2 - Safety", when I save the Introduction chapter as "EFG 1 - Introduction" it will still retain the xref to "ABC 2 - Safety".
Right now, the only way to see if there are xrefs pointing to latent docs, is to check each one manually. If the xref panel displayed a column indicating the filename of the linked documents, I would be able to tell at a glance if that xref was pointing to the wrong document.
Thank you.
ID CS5, MAC

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross references in structured documents

Hi there,
Perhaps someone of you has a tip for me regarding cross references in structured FrameMaker.
The problem we have at the moment:
We were working with FM8 structured. But - as we worked with FM documents most of the times - very often the xml files are not on the latest version.
When we now want to update these documents with FM9 and save them as xml documents, there are lot's of errors that the attribute type is not defined for the element fm-xref.
Perhaps some of you know this error message.
At the moment we do exchange all those cross reference for new ones.
Of course, when we have a xml document which contains the latest status, this is not a problem.
You just open the xml file and save it as FM9 document. No problem with any cross reference...
But what can I do with those FM8 documents?
Would it help to use some application just for fixong the cross references in those (if possible)?
This definitly seems to be an error in FM itself.
Is there perhaps some fix for FM9 I don't know about?
And how about FM10: Will I have the same problems, if we switch to that version?
Regards,
Anna

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Cross References in ID CC

I've seen cross reference questions, but none dealing with ID CC, which, I believe is 64-bit.
We've greatly expanded our use of cross-references with this new more power version with overall good success. However, ID still seems to insist on updating every cross-reference with every keystroke. What a pain.
I work with all book documents open to minimize this, but since it's across a network, it can still be pretty painful. In addition, some documents are used in multiple books so I use layers to control which cross-references are active any any given time.
It's getting very trying. Does anyone have experience with using 3rd party xref management software with ID CC?

Hi Van,
I fear, I expressed myself not very clear. I try again.
We have DITA structured documents. However, lastest status often was saved in the FM document. The xml documents often are not representing the final status.
When I open the FM8 document in FM9 everything looks pretty good.
But: When I want to save the document as xml with FM9, I'm getting errors regarding the cross references.
The cross references which were created in FM8 - doesn't matter, if a valid xml document or a FM document - always look the same.
(BTW: I don't think that in structured documents cross references always refer to elemts with a unique ID.)
example from xml which was created with FM8:
<xref href = "#id08B4A0R30E9" type = "fm:Chapter">"..."</xref>
the only difference in the FM document is that the element is called fm-xref there, as it's not an external url.
in FM9 those cross references are totally different.
example from xml which was created in FM9:
<xref href = "#id08B4A0R30E9" class = "- topic/xref">"..."</xref>
When saving the FM documents with the cross references from the first example as xml in FM9 (we don't have FM8 anymore), I get an error that the attribute type is not defined.
When having a xml document that was last changed with FM8 and opening/ saving this with FM9, there is no error.
At the moment I do not know how to solve this issue.
And also I'm not sure weather the same problem might accour again with change from FM9 to FM10 or else.
It is a great effort to make new cross references just because we upgraded from FM8 to FM9. (And of course always at most inconvienent time.)
As we are thinking of upgrading to FM10, it would be good to know before, if there are any similar issues to expect.
Or if there is an fix for FM9 or FM10 to avoid this at all.
Regards,
Anna

Use enum or subclassing to differentiate between different elements?

Hello all,
I have a design decision to make.
I have two different Elements with everything the same except the name.
So I have two ideas on how this can be solved.
1. Through subclassing.
2. Through enumeration.
I have tried to make two examples of this so you can recommend 1 or 2 only on a conceptual level not implementation.
Sub classing
public class Element {
     //Methods
public class A extends Element {
     //Nothing
public class B extends Element {
     //Nothing
public class Main {
     public static void main(String[] args) {
          Element elm = new A();
          if (elm instanceof A){}
          else if (elm instanceof B){}
}Enumeration
public class Element {
     public enum Type {A, B}
     private Type type;
     public Element(Type type) {
          this.type = type;
     public Type getType() {
          return type;
     //Methods
public class Main {
     public static void main(String[] args) {
          Element elm = new Element(Type.A);
          switch(elm.getType()) {
               case A:
               case B:
}Thanks /Farmor
Edited by: Farmor on Dec 15, 2009 3:14 PM (Spelling error)

Thanks for the answers.
Then I will go with the enum solution that will give me a lot of free things.
Such as I can limit the API user to only choose between my predefined values and the use of my API will be much easier when used in a good IDE.
/Farmor

DAO Pattern: Organization and cross references

Hello,
in general I have very good experiences using DAOs. But there are two issues, which becloud the pattern
in my cases.
First, I am using Hibernate and strongly depend on custom entity names. So when I use a DAO, say
CustomerDAO, and need to use a join to create the result of all Products which were buyed by some
customers, I need to know the entityName carried by the ProdcutDAO. Technically this is no problem,
because CustomerDAO can instantiate a leightweight ProductDAO and retrieve the name. But then
I have a cross references between two DAOs, which couples them more, than it should be.
Another concern is to decide which operation belongs to a DAO. If I join some customer data with address
data (another entity) and some product data (e.g. find all name and adress of customer, which have a product
bought today) and have no self-contained type for this result, which DAO gets the method?

Serethos_0 wrote:
Hello,
in general I have very good experiences using DAOs. But there are two issues, which becloud the pattern
in my cases.
First, I am using Hibernate and strongly depend on custom entity names. So when I use a DAO, say
CustomerDAO, and need to use a join to create the result of all Products which were buyed by some
customers, I need to know the entityName carried by the ProdcutDAO. Technically this is no problem,
because CustomerDAO can instantiate a leightweight ProductDAO and retrieve the name. But then
I have a cross references between two DAOs, which couples them more, than it should be.
Sometimes coupling cannot be avoided. Especially in situations where you a priori know that you will need a whole graph of objects returned (regardless of whether they are fetched eagerly or lazily). You can write a composite object that links the two together. [https://www.hibernate.org/86.html]
Another concern is to decide which operation belongs to a DAO. If I join some customer data with address
data (another entity) and some product data (e.g. find all name and adress of customer, which have a product
bought today) and have no self-contained type for this result, which DAO gets the method?I think the clue is in your own response "have no self-contained type for this result". Generally, you should create an object (and in many cases an interface) for anything important. That's point #1. Another point is that you can have composite data access objects (DAO's that simply chain other DAO's together). Or, if you are opting for a service-oriented architecture [http://en.wikipedia.org/wiki/Service-oriented_architecture], the service is a logical place to put this logic chaining DAO's together.
- Saish

Want to build a composite EAR by referencing two ears.

Hi all,
I have two ejb projects and two individual ears for them. and in each project i have only one session bean and i made it as a web service.Now i want make a single composite ear by adding refenrences of that ears in application-j2ee-engine.xml. But option to build ear is disabled. So how can i build that ear and deploy into Web AS.
Regards,
Kiran.

You can make a single composite EAR by referencing two different EJB projects. Not by referencing two different EAR projects ...makes no sense. EAR is a indpendent deployable unit . Instead of creating different EARs and referening them, add the two EJB projects to your composite EAR project and you should be able to build / deploy it then as a whole unit.

How to use same DFF for two different forms with :BLOCK.field reference

Hi,
Can anyone suggest how to use the same dff in two different forms by using :BLOCK.field reference.
Scenario is the same DFF is referenced by two forms, viz. Form-1 & Form-2.
Form-1 Reference Field is :BLOCK.field name, but the same block is not available in Form-2, which throws an error while opening it.
Any pointers please.
Thanks,

In the environment I currently have access to do not have similar setup.
Let say you setup the DFF1 default value to $HEADER.customer_name, the name of the DFF is CUSTOMER_NAME, description can be anything.
In DFF2, default value should be a SQL, where you can reference the DFF1. For example, SELECT DECODE($FLEX.CUSTOMER_NAME, 'ABC', 1, 'DEF', 2, NULL) FROM dual
In this case, you can reference the DFF1.

Error after creating Element level join between two different dataset in11G

Hi Experts,
My report is having data from two different datsets, I created two datasets and joined them with Element Level join. I am getting below error.
"The following tags were not closed: DATA_DS. Error processing resource 'http://localhost:9704/xmlpserver/servlet/xdo'. "
But independent datasets are executing with out any errors.
Please let me know, If any one have inputs to resolve this.
Thanks in advance..

Hi,
Can you please explain the resolution in more details. I'm also having the same issue in BI Publisher report when trying to join two data sets with Element Level Link. I have checked that all my columns have alias names.
Thanks,
Piya.
Edited by: 947289 on Jul 18, 2012 5:56 AM

How to Display two different objects in a single table header in Cross Tab?

i All,
I've a reqiurement for a Cross Tab Report like I need two different objects that should be displayed side-by-side, one object's values after another in a single header. In the picture below I've shown the objects separately in two rows, top header having BSNLNL,MTNLNL,RCOMNL and Header-2 having AIRTIL,RCOMIL. But requirements needs to be showing like this,
BSNLNL
MTNLNL
RCOMNL
AIRTIL
RCOMIL
Actually, the data for the header comes from a single object called Operator. I've show the Operators name ending with NL and after that names ending with IL. So, i've separated the data into two variables using the below formulae.
IL:
=[Billing Operator]
Where
Match([Billing Operator];"*IL")=1
NL:
=[Billing Operator]
Where
Match([Billing Operator];"*NL")=1
Also, the NL data should start first and after the NL data's last value ends, the IL data should begin.
One more thing is that I've to show '0' for null values. So i've used the below formulae on the column data. You can see below that except the "Outgoing ILD Mins in the month from Mobile Network" everything else showing fine. I don't understand why.
=If
Substr([Franchise];3;1)="M"
Then
   [Mobile Outgoing Charged Usage Minutes]
   Else
   0
I tried different approaches but couldn't find a solution. Could you please help me?
I'm using BO WebI 4.1 SP1
Regards,
Naren Vema.

Hi Naren,
No need to split Billing Operator object. Create a variable-
V_IL_NL= If Match([Billing Operator];"*IL")=1 Then "IL" ElseIf Match([Billing Operator];"*NL")=1 Then "NL"
1) Put V_IL_NL variable below Billing Operator object header.
2) Sort and create break on this variable.
3) Delete Footer column. it will automatically create when you apply break.
4) Hide V_IL_NL variable from this header.
~Anuj

Cross reference data from 2 different ecc system.

Hi Sdners,
Iam working on a scenario where i have to get data from two different Ecc system,consolidate them and send it back to their respective system.
But some refernce data in both the systems are different and when iam merging data from 2 system i have to maintain either of the reference data.But problem comes when i syndicate it back to ECC ,it cannot accept a new reference data.
Please suggest me some answere how to proceed in such case.
Its urgent.
Points will be rewarded for Genuine answeres.
Thanks in advance,
Regards,
Neethu.

Hi,
First enable keymapping property to YES for the table which you want to do
importing and syndicatig.
Create two remote systems type inbound/outbound .
Import the data from first remote system and map the corresponding fields.
Don't forget to map the remotekey field which is on the destination side.Make clone
of one of the dispaly field and map to the remote key field.
After importing you can see the records from which remote system are imported
using Edit Key Mappings option in DataManager.It shows that remotesystem
name and corresponding remote key.
Do the same for second remote system too.
After merging data in data manager , you can see the merged record and see the
two remote systems names and two remote keys by using Edit Key Mappings
option so the merged record goes back to both remote systems when you syndicate
the records.
Syndicate the data from first remote system by selecting destination properties and
output remote system property under map properties tab as your first remote
system.
Do the mapping for corresponding fields and don't forget to map the value field under
remote key .Then MDM generates remote keys for only records belongs to your
first remote system.You can see this in destination preview.It does n't genarate
remote keys for second remote system.Then check the option Suppress records
without key under map properties tab and execute the syndication.Finally we can
see the accurate records.
Do the same for second remote system too.
Hope it helps
Cheers
Narendra

I have "chatted" with customer service 5 different times. I was sent here. I have activated Photoshop Elements 9 on two different iMacs. They are both dead and I am unable to get it to activate on my newest computer. iMac. Can anybody help me?

I have "chatted" with customer service 5 different times. I was sent here. I have activated Photoshop Elements 9 on two different iMacs. They are both dead and I am unable to get it to activate on my newest computer. iMac. Can anybody help me?

Unfortunately, only adobe can help you with that, as most people here are just posters such as your self and don't work for adobe.
If you go here and use the Chat now button (bottom of page), they should get you up and running by resetting your activations.
http://helpx.adobe.com/x-productkb/policy-pricing/activation-deactivation-products.html

Cross-references referencing two different elements...

Similar Messages

Maybe you are looking for