I am also working on bringing that exact field into the Priority
Dispatch Report right now. I'm on V8.03.404.
I don't know anything about the JCR65 table other than it has been a
source of headache for me in the priodisp Report Data Definition for
the past 2 weeks.
Last week, I believe that I identified a bug in this RDD (Report Data
Definition). I did not log a Support call because, in my experience,
reporting bugs to Epicor takes up far too much of my time in "proving"
that it is a bug. I haven't had the time to spare recently.
The bug is that whenever you attempt to add a Relationship to the JCR65
table, there appear to be no fields in JCR65 available for linking.
Just last night, I found out how to get past this.
Add the JobOper table to your RDD just as you normally would add any
other table. Then include the fields you want from JobOper plus all
fields you will require for fixing the links in Crystal:
JobOper.Company
JobOper.JobNum
JobOper.AssemblySeq
JobOper.PartNum
JobOper.RunQty
JobOper.QtyCompleted
Then add a Relationship between the JCR65 table and the JobOper table.
You don't need a key; you can leave that field blank. Then SAVE.
Then, here is how you overcome the apparent bug: Press the Add
Relationship Field button then simply type Company in the Parent
fieldname box. It turns out that even though there is no available
list of fields, you can still type them in.
Add these relationships:
JCR65.Company = JobOper.Company
JCR65.JobNum = JobOper.JobNum
JCR65.AssemblySeq = JobOper.AssemblySeq
This should work. I had success last night adding the
CustXPrt.XPartNum to this Priority Dispatch Report. Today I am trying
to add the JobOper.QtyCompleted just as you are.
Lynn
Dispatch Report right now. I'm on V8.03.404.
I don't know anything about the JCR65 table other than it has been a
source of headache for me in the priodisp Report Data Definition for
the past 2 weeks.
Last week, I believe that I identified a bug in this RDD (Report Data
Definition). I did not log a Support call because, in my experience,
reporting bugs to Epicor takes up far too much of my time in "proving"
that it is a bug. I haven't had the time to spare recently.
The bug is that whenever you attempt to add a Relationship to the JCR65
table, there appear to be no fields in JCR65 available for linking.
Just last night, I found out how to get past this.
Add the JobOper table to your RDD just as you normally would add any
other table. Then include the fields you want from JobOper plus all
fields you will require for fixing the links in Crystal:
JobOper.Company
JobOper.JobNum
JobOper.AssemblySeq
JobOper.PartNum
JobOper.RunQty
JobOper.QtyCompleted
Then add a Relationship between the JCR65 table and the JobOper table.
You don't need a key; you can leave that field blank. Then SAVE.
Then, here is how you overcome the apparent bug: Press the Add
Relationship Field button then simply type Company in the Parent
fieldname box. It turns out that even though there is no available
list of fields, you can still type them in.
Add these relationships:
JCR65.Company = JobOper.Company
JCR65.JobNum = JobOper.JobNum
JCR65.AssemblySeq = JobOper.AssemblySeq
This should work. I had success last night adding the
CustXPrt.XPartNum to this Priority Dispatch Report. Today I am trying
to add the JobOper.QtyCompleted just as you are.
Lynn
--- In vantage@yahoogroups.com, "k2lamm" <karl_a_lamm@...> wrote:
>
> I am trying to modify the Priority Dispatch Report and replace the
RUN
> QTY field with the QTY COMPLETE. This requires that I add the JobOper
> table but I cannot get it to work. I was told I have a link problem
> because the XML has no JobOper data in it. The Crystal Database
Expert
> shows a table "JCR65"; I am trying to link to that table. I do not
know
> much about this table - it is not included in the Data Dictionary
> Viewer and I suspect that might be part of the problem. Any ideas?
> Thanks.
>