Documenting use of user defined fields

Yahoo Archive
1
We just keep an excel sheet to indicate what ud fields and tables are in use, what programmer is using them (and in what apps) and what they represent to us (and/or where the data the contain came from in our legacy system and/or where we might be archiving the data in our off line db so we have a continuous source of data now reaching back into the early 90's accumulated across 4 systems).



--- On Mon, 7/7/08, Calvin Krusen <ckrusen@...> wrote:

From: Calvin Krusen <ckrusen@...>
Subject: [Vantage] Documenting use of user defined fields
To: vantage@yahoogroups.com
Date: Monday, July 7, 2008, 8:41 AM






Does anyone have a method of documenting the use of User Defined fields?

I was thinking about editing the data dictionary (just the field's
description) so it reflects the use of that field in the context of our
customization.

Or is that not the best way to do it? Also, wouldn't the data
dictionary get overwritten on any version updates?

Calvin
2
Does anyone have a method of documenting the use of User Defined fields?

I was thinking about editing the data dictionary (just the field's
description) so it reflects the use of that field in the context of our
customization.

Or is that not the best way to do it? Also, wouldn't the data
dictionary get overwritten on any version updates?

Calvin
3
We are using an Excel Spreadsheet - Not an ideal solution.
With the advent of customization maintenance in 8.03.4xx One would
think it would be possible to parse the XML of the customization(s)
looking for references to UD fields and display them in a list.....

--- In vantage@yahoogroups.com, "Calvin Krusen" <ckrusen@...> wrote:
>
> Does anyone have a method of documenting the use of User Defined
fields?
>
> I was thinking about editing the data dictionary (just the field's
> description) so it reflects the use of that field in the context of
our
> customization.
>
> Or is that not the best way to do it? Also, wouldn't the data
> dictionary get overwritten on any version updates?
>
> Calvin
>
4
I didn't think it was possible to update the data dictionary. I created
a folder on my Epicor share and it holds exported customization and a
text file that documents the UD fields


Kersten MacLennan
IT/ERP Analyst
Semrock, Inc.
3625 Buffalo Rd.,
Suite 6
Rochester, NY 14624
585-594-7009
585-594-7095 fax

kmaclennan@...

The Standard in Optical Filters for Biotech & Analytical Instrumentation


Hundreds of Thousands of Ion Beam Sputtered filters delivered -
extensive inventory now!

The information contained in this message and any attachments may be
privileged, confidential, and protected from disclosure. If the reader
of this message is not the intended recipient, or any agent responsible
for delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, or copying of this
communication may be unlawful and therefore strictly prohibited. If you
received this message in error, please reply to the message and delete
it. Thank you




________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Calvin Krusen
Sent: Monday, July 07, 2008 8:41 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Documenting use of user defined fields



Does anyone have a method of documenting the use of User Defined fields?

I was thinking about editing the data dictionary (just the field's
description) so it reflects the use of that field in the context of our
customization.

Or is that not the best way to do it? Also, wouldn't the data
dictionary get overwritten on any version updates?

Calvin






[Non-text portions of this message have been removed]
5
I think attempting to update the data dictionary is probably a bad
idea. I tried it on the Test Company db, and got unexpected results.

I stopped the TestCo DB and appservers, launched the OpenEdge DB
Admin tool, connected to the TestCo db, changed the description and
column title of the ShortChar01 field of the QuoteDtl table, and
committed the changes to the db.

After re-starting the db and launching the testCo, the Data
Dictionary Viewer displayed the new coulmm title, but the description
still showed "not used". I went back and double checked the db using
the OE admin tool, and description field showed my changes.

Anyway... Documenting the user fields in a simple Excel file will
have to do.

Calvin Krusen

--- In vantage@yahoogroups.com, "Kersten MacLennan" <kmaclennan@...>
wrote:
>
> I didn't think it was possible to update the data dictionary. I
created
> a folder on my Epicor share and it holds exported customization and
a
> text file that documents the UD fields
>
>
> Kersten MacLennan
> IT/ERP Analyst
> Semrock, Inc.
> 3625 Buffalo Rd.,
> Suite 6
> Rochester, NY 14624
> 585-594-7009
> 585-594-7095 fax
>
> kmaclennan@...
>
> The Standard in Optical Filters for Biotech & Analytical
Instrumentation
>
>
> Hundreds of Thousands of Ion Beam Sputtered filters delivered -
> extensive inventory now!
>
> The information contained in this message and any attachments may be
> privileged, confidential, and protected from disclosure. If the
reader
> of this message is not the intended recipient, or any agent
responsible
> for delivering this message to the intended recipient, you are
hereby
> notified that any dissemination, distribution, or copying of this
> communication may be unlawful and therefore strictly prohibited. If
you
> received this message in error, please reply to the message and
delete
> it. Thank you
>
>
>
>
> ________________________________
>
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
Behalf
> Of Calvin Krusen
> Sent: Monday, July 07, 2008 8:41 AM
> To: vantage@yahoogroups.com
> Subject: [Vantage] Documenting use of user defined fields
>
>
>
> Does anyone have a method of documenting the use of User Defined
fields?
>
> I was thinking about editing the data dictionary (just the field's
> description) so it reflects the use of that field in the context of
our
> customization.
>
> Or is that not the best way to do it? Also, wouldn't the data
> dictionary get overwritten on any version updates?
>
> Calvin
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>