Tracing Options - Log File

The trace log, and for that matter, the fields the customization point to,
are "datasets". These usually correspond to tables, but as you noticed,
they're not always a perfect match.


For example, if you do a GetByID in Order Entry, that method returns a Sales
Order dataset. The OrderHed table has the CustNum field, and to maintain
database normalization, if you want the CustID or Customer Name, you'd have
to go to the Customer table to get those fields. However, the GetByID may
return those fields as well in the dataset. They are not part of the
OrderHed table, but they are a field within the OrderHed dataset.



As far as rules for where to find them, I haven't found anything other than
detective work, lots of experience, and boards such as this.



HTH,

Kevin Simon

SimsTrak Consulting



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
cooner_55421
Sent: Saturday, January 15, 2011 11:53 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Tracing Options - Log File







>
> Data dictionary viewer

Thanks but not really what I meant.

The tracer is usually a nice fast way to see all the tables/fields involved
after you save a record.
But, every once in while, the trace log will lists a field that really
doesn't exist.
I'm wondering what is going on in these cases?





[Non-text portions of this message have been removed]
Data dictionary viewer works fine its under Utilz

*Jose C Gomez*
*Software Engineer*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>

*Quis custodiet ipsos custodes?*



On Fri, Jan 14, 2011 at 6:20 PM, cooner_55421 <cooner_55421@...>wrote:

>
>
> Hi,
>
> I use the Tracing Options log to ID table/field names.
> It's pretty fast and works most of the time, but not always.
> Anybody else noticed this?
> Are there any tips on when to finding the real table/field names?
> Right now, I mostly just guess and query tables until I find my value.
>
> Here is an example:
> I changed the UPC12 on the UOM form.
> Trace log shows this:
> <PartUOM>
> <UPC12>12345</UPC12>
> </PartUOM>
> The value really ends up in the PartPC table.
>
> When I open the part form in developer mode.
> txtUPC12 has:
> EpiBinding of PartUOM.UPC12
> EpicContextMenuKey is PartPC.ProdCode
>
> Can somebody explain the mechanics of this for me?
>
> Thanks
>
>
>


[Non-text portions of this message have been removed]