Best Practices for UD Field Reference

Yahoo Archive
1
Yes I had fields in UD Tables and they did migrate correctly (mostly) it didn't like integers at the time (500xx migration) so I changed them all to decimals and it worked. Not sure since the 600 release I haven't upgraded again. Working on the same 500 upgrade I did, just brought it up to 600.4 without problems.

Thanks!


Jose C Gomez
Software Engineer


T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 10:40 AM, Ted Koch tkoch77@... [vantage] <vantage@yahoogroups.com> wrote:
 
<div>
  
  
  <p></p><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:8pt;"><div><span>I mean the fields I created myself using Extended UD Table migration cause an error and the migration to never successfully finish.</span></div>

Did you have any fields added to a table this way before you migrated (if you have tried any migration yet)?


From: "Jose Gomez jose@... [vantage]" <vantage@yahoogroups.com>

To: Vantage <vantage@yahoogroups.com>

Sent: Tuesday, June 17, 2014 10:09 AM

Subject: Re: [Vantage] Best Practices for UD Field Reference



All custom fields ShortChar, Characer, NUmber etc.. if they are in use they are copied over to the Extended UD if they are null then they will be removed.


Jose C Gomez
Software Engineer



T: 904.469.1524 mobile
E: jose@...

http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 10:06 AM, Ted Koch tkoch77@... [vantage] <vantage@yahoogroups.com> wrote:
 
<div>
  
  
  <div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:8pt;"><div><span>I have a call open with support where I had an issue migrating from E9 to E10.</span></div>

During the UD fields migration it was throwing an error on tables that I had extended using the Extended UD Table Maintenance. The extended table fields never get “copied” over.


If I delete the Extended UD tables in the maintenance window and then migrate I get no errors, but the fields obviously don’t get copied.

From: "Jose Gomez jose@... [vantage]" <vantage@yahoogroups.com>

To: Vantage <vantage@yahoogroups.com>
Sent: Tuesday, June 17, 2014 9:12 AM

Subject: Re: [Vantage] Best Practices for UD Field Reference




Also on the for what is worth category if you are in 9.05.XX I recommend you use the custom UD fields and not the standard CHaracterXXÂ
1) It gives you ability to know the name of the field as you had intended it vs CharacterXX
  1. In E10 all the CharacterXX fields go away in favor of the new style. So if you already have them there you are ahead of the curve


Jose C Gomez

Software Engineer

T: 904.469.1524 mobile

E: jose@...

http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 8:58 AM, 'Terry M. Hall' THALL@... [vantage] <vantage@yahoogroups.com> wrote:
 
<div>
  
  
  <div>Hi,

We use the Extended Property Maintenance screen. Fill in the Label name with a description of the UD field. We also put a unique prefix in the description field and use that to filter a dashboard.

[Users:PUBLIC:Advertising:LOGO TYPES:VECTOR LOGO ADS.ai]

Terrance Hall | Techincal Support Supervisor




Thall@...<mailto:jboll@...> | [P] 563.583.7311, Ext. 5247 [F] 800.832.9296
More than a brand. We’re a family.

CONFIDENTIALITY NOTICE:
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference




Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you’ve utilized. Typically UD fields have a presence on program UIs so it’s been useful to keep track of customization change logs but it’s not infallible. Any advice for someone doing an implementation and wanting to start it out right?




Thanks,



Kyle


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

</div>
 


<div style="color:#fff;min-height:0;"></div>






</div>
 


<div style="color:#fff;min-height:0;"></div>






</div><div><div class="ygrps-yiv-2057037102h5">
 


<div style="color:#fff;min-height:0;"></div>

2

Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you've utilized.  Typically UD fields have a presence on program UIs so it's been useful to keep track of customization change logs but it's not infallible.  Any advice for someone doing an implementation and wanting to start it out right?


Thanks, 


Kyle

3
Use extended properties (under Utilities)…fill out this area and then you can write a report on it to see what you have used!



M. Manasa Reddy
manasa.reddy@...
[d] 281-994-3483
[c] 773-401-4126

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference



Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you've utilized. Typically UD fields have a presence on program UIs so it's been useful to keep track of customization change logs but it's not infallible. Any advice for someone doing an implementation and wanting to start it out right?



Thanks,



Kyle



[Non-text portions of this message have been removed]
4
Hi,
We use the Extended Property Maintenance screen. Fill in the Label name with a description of the UD field. We also put a unique prefix in the description field and use that to filter a dashboard.

[Users:PUBLIC:Advertising:LOGO TYPES:VECTOR LOGO ADS.ai]

Terrance Hall | Techincal Support Supervisor




Thall@...<mailto:jboll@...> | [P] 563.583.7311, Ext. 5247 [F] 800.832.9296
More than a brand. We’re a family.

CONFIDENTIALITY NOTICE:
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference



Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you've utilized. Typically UD fields have a presence on program UIs so it's been useful to keep track of customization change logs but it's not infallible. Any advice for someone doing an implementation and wanting to start it out right?



Thanks,



Kyle



[Non-text portions of this message have been removed]
5
Within our internal Sharepoint I have created an Epicor section and in there keep track of which UD fields are in use by table. Each table is represented as a folder and in the folder is the list of fields in use.

From: "jockthemotie@... [vantage]" <vantage@yahoogroups.com>
To: vantage@yahoogroups.com
Sent: Tuesday, June 17, 2014 8:50 AM
Subject: [Vantage] Best Practices for UD Field Reference



Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you've utilized.  Typically UD fields have a presence on program UIs so it's been useful to keep track of customization change logs but it's not infallible.  Any advice for someone doing an implementation and wanting to start it out right?

Thanks, 

Kyle




6
Also on the for what is worth category if you are in 9.05.XX I recommend you use the custom UD fields and not the standard CHaracterXXÂ
1) It gives you ability to know the name of the field as you had intended it vs CharacterXX
  1. In E10 all the CharacterXX fields go away in favor of the new style. So if you already have them there you are ahead of the curve


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile

E: jose@…

http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 8:58 AM, 'Terry M. Hall' THALL@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>Hi,

We use the Extended Property Maintenance screen. Fill in the Label name with a description of the UD field. We also put a unique prefix in the description field and use that to filter a dashboard.

[Users:PUBLIC:Advertising:LOGO TYPES:VECTOR LOGO ADS.ai]

Terrance Hall | Techincal Support Supervisor




Thall@...<mailto:jboll@...> | [P] 563.583.7311, Ext. 5247 [F] 800.832.9296
More than a brand. We’re a family.

CONFIDENTIALITY NOTICE:
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.


From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference




Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you’ve utilized. Typically UD fields have a presence on program UIs so it’s been useful to keep track of customization change logs but it’s not infallible. Any advice for someone doing an implementation and wanting to start it out right?




Thanks,



Kyle


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

</div>
 


<div style="color:#fff;min-height:0;"></div>

7
We're on Vantage and don't think we have Extended Property Maintenance, but I have a spreadsheet and I log all customisations on there (Custom Forms and reason, UD fields, BPM's, etc).
8
Jose, 

Can you expand on this?  The implementation we're doing is currently E9.05.702 however there's been discussion of a move to E10, and if there's anything I can do now to future proof it.  These custom UD fields are purely created in Extended properties right?
9
Correct

There is an Extended UD Table Maintenance that allows you to create Table_UD (OrderHed_UD, InvoiceHed_UD… etc)


On these tables then you can add your custom fields MyCustomField and use them throughout the system as if they were part of the Initial Table (with a few caveats for reporting where you'll have to bring in the MyTable_UD table and join it in the ForeignSysRowID field


If you do this in 9.05 then when you upgrade to 10 you'll be already in the new format so you'll have an advantage there as well as giving you more control over the naming of your fieldsÂ




Jose C Gomez
Software Engineer


T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 9:22 AM, jockthemotie@... [vantage] <vantage@yahoogroups.com> wrote:

 
<div>
  
  
  <p>Jose, </p><div><br></div><div>Can you expand on this?  The implementation we&#39;re doing is currently E9.05.702 however there&#39;s been discussion of a move to E10, and if there&#39;s anything I can do now to future proof it.  These custom UD fields are purely created in Extended properties right?</div>


</div>
 


<div style="color:#fff;min-height:0;"></div>

10
Jose,
Can you tell me if it is just the CharacterXX fields going away, or all of those UD fields like ShortCharXX, NumberXX, etc...



Thanks,
Matt Caldwell
11
I have a call open with support where I had an issue migrating from E9 to E10.

During the UD fields migration it was throwing an error on tables that I had extended using the Extended UD Table Maintenance. The extended table fields never get "copied" over.

If I delete the Extended UD tables in the maintenance window and then migrate I get no errors, but the fields obviously don't get copied.

From: "Jose Gomez jose@... [vantage]" <vantage@yahoogroups.com>
To: Vantage <vantage@yahoogroups.com>
Sent: Tuesday, June 17, 2014 9:12 AM
Subject: Re: [Vantage] Best Practices for UD Field Reference

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800 --

#ygrps-yiv-961651066yiv9901943800 .ygrps-yiv-961651066yiv9901943800ygrp-photo-title{
clear:both;font-size:smaller;height:15px;overflow:hidden;text-align:center;width:75px;}
#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800ygrp-photo{
background-position:center;background-repeat:no-repeat;background-color:white;border:1px solid black;height:62px;width:62px;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800photo-title
a,
#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800photo-title a:active,
#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800photo-title a:hover,
#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800photo-title a:visited {
text-decoration:none;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800attach-table div.ygrps-yiv-961651066yiv9901943800attach-row {
clear:both;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800attach-table div.ygrps-yiv-961651066yiv9901943800attach-row div {
float:left;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 p {
clear:both;padding:15px 0 3px 0;overflow:hidden;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800ygrp-file {
width:30px;}
#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800attach-table div.ygrps-yiv-961651066yiv9901943800attach-row div div a {
text-decoration:none;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800attach-table div.ygrps-yiv-961651066yiv9901943800attach-row div div span {
font-weight:normal;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 div.ygrps-yiv-961651066yiv9901943800ygrp-file-title {
font-weight:bold;}
#ygrps-yiv-961651066
#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800 –
#ygrps-yiv-961651066yiv9901943800ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800ygrp-mkp hr {
border:1px solid #d8d8d8;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800ygrp-mkp #ygrps-yiv-961651066yiv9901943800hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800ygrp-mkp #ygrps-yiv-961651066yiv9901943800ads {
margin-bottom:10px;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800ygrp-mkp .ygrps-yiv-961651066yiv9901943800ad {
padding:0 0;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800ygrp-mkp .ygrps-yiv-961651066yiv9901943800ad p {
margin:0;}

#ygrps-yiv-961651066 #ygrps-yiv-961651066yiv9901943800 #ygrps-yiv-961651066yiv9901943800ygrp-mkp .ygrps-yiv-961651066yiv9901943800ad a {
color:#0000ff;text-decoration:none;}
#ygrps-yiv-961651066



Also on the for what is worth category if you are in 9.05.XX I recommend you use the custom UD fields and not the standard CHaracterXX 
1) It gives you ability to know the name of the field as you had intended it vs CharacterXX
  1. In E10 all the CharacterXX fields go away in favor of the new style. So if you already have them there you are ahead of the curve


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 8:58 AM, 'Terry M. Hall' THALL@... [vantage] <vantage@yahoogroups.com> wrote:
  
<div>
  
  
  <div>Hi,

We use the Extended Property Maintenance screen. Fill in the Label name with a description of the UD field. We also put a unique prefix in the description field and use that to filter a dashboard.

[Users:PUBLIC:Advertising:LOGO TYPES:VECTOR LOGO ADS.ai]

Terrance Hall | Techincal Support Supervisor




Thall@...<mailto:jboll@...> | [P] 563.583.7311, Ext. 5247 [F] 800.832.9296
More than a brand. We’re a family.

CONFIDENTIALITY NOTICE:
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference




Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you’ve utilized. Typically UD fields have a presence on program UIs so it’s been useful to keep track of customization change logs but it’s not infallible. Any advice for someone doing an implementation and wanting to start it out right?




Thanks,



Kyle


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

</div>
 


<div style="color:#fff;min-height:0;"></div>





12
All custom fields ShortChar, Characer, NUmber etc.. if they are in use they are copied over to the Extended UD if they are null then they will be removed.


Jose C Gomez
Software Engineer



T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com

     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 10:06 AM, Ted Koch tkoch77@... [vantage] <vantage@yahoogroups.com> wrote:
 
<div>
  
  
  <p></p><div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:8pt;"><div><span>I have a call open with support where I had an issue migrating from E9 to E10.</span></div>

During the UD fields migration it was throwing an error on tables that I had extended using the Extended UD Table Maintenance. The extended table fields never get “copied” over.


If I delete the Extended UD tables in the maintenance window and then migrate I get no errors, but the fields obviously don’t get copied.

From: "Jose Gomez jose@... [vantage]" <vantage@yahoogroups.com>

To: Vantage <vantage@yahoogroups.com>
Sent: Tuesday, June 17, 2014 9:12 AM

Subject: Re: [Vantage] Best Practices for UD Field Reference




Also on the for what is worth category if you are in 9.05.XX I recommend you use the custom UD fields and not the standard CHaracterXXÂ
1) It gives you ability to know the name of the field as you had intended it vs CharacterXX
  1. In E10 all the CharacterXX fields go away in favor of the new style. So if you already have them there you are ahead of the curve


Jose C Gomez

Software Engineer

T: 904.469.1524 mobile

E: jose@...

http://www.josecgomez.com
     Â


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 8:58 AM, 'Terry M. Hall' THALL@... [vantage] <vantage@yahoogroups.com> wrote:
 
<div>
  
  
  <div>Hi,

We use the Extended Property Maintenance screen. Fill in the Label name with a description of the UD field. We also put a unique prefix in the description field and use that to filter a dashboard.

[Users:PUBLIC:Advertising:LOGO TYPES:VECTOR LOGO ADS.ai]

Terrance Hall | Techincal Support Supervisor




Thall@...<mailto:jboll@...> | [P] 563.583.7311, Ext. 5247 [F] 800.832.9296
More than a brand. We’re a family.

CONFIDENTIALITY NOTICE:
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference




Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you’ve utilized. Typically UD fields have a presence on program UIs so it’s been useful to keep track of customization change logs but it’s not infallible. Any advice for someone doing an implementation and wanting to start it out right?




Thanks,



Kyle


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

</div>
 


<div style="color:#fff;min-height:0;"></div>






</div>
 


<div style="color:#fff;min-height:0;"></div>

13
I mean the fields I created myself using Extended UD Table migration cause an error and the migration to never successfully finish.

Did you have any fields added to a table this way before you migrated (if you have tried any migration yet)?

From: "Jose Gomez jose@... [vantage]" <vantage@yahoogroups.com>
To: Vantage <vantage@yahoogroups.com>
Sent: Tuesday, June 17, 2014 10:09 AM
Subject: Re: [Vantage] Best Practices for UD Field Reference

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967 --

#ygrps-yiv-187547347yiv2892874967 .ygrps-yiv-187547347yiv2892874967ygrp-photo-title{
clear:both;font-size:smaller;height:15px;overflow:hidden;text-align:center;width:75px;}
#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967ygrp-photo{
background-position:center;background-repeat:no-repeat;background-color:white;border:1px solid black;height:62px;width:62px;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967photo-title
a,
#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967photo-title a:active,
#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967photo-title a:hover,
#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967photo-title a:visited {
text-decoration:none;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967attach-table div.ygrps-yiv-187547347yiv2892874967attach-row {
clear:both;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967attach-table div.ygrps-yiv-187547347yiv2892874967attach-row div {
float:left;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 p {
clear:both;padding:15px 0 3px 0;overflow:hidden;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967ygrp-file {
width:30px;}
#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967attach-table div.ygrps-yiv-187547347yiv2892874967attach-row div div a {
text-decoration:none;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967attach-table div.ygrps-yiv-187547347yiv2892874967attach-row div div span {
font-weight:normal;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 div.ygrps-yiv-187547347yiv2892874967ygrp-file-title {
font-weight:bold;}
#ygrps-yiv-187547347
#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967 –
#ygrps-yiv-187547347yiv2892874967ygrp-mkp {
border:1px solid #d8d8d8;font-family:Arial;margin:10px 0;padding:0 10px;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967ygrp-mkp hr {
border:1px solid #d8d8d8;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967ygrp-mkp #ygrps-yiv-187547347yiv2892874967hd {
color:#628c2a;font-size:85%;font-weight:700;line-height:122%;margin:10px 0;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967ygrp-mkp #ygrps-yiv-187547347yiv2892874967ads {
margin-bottom:10px;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967ygrp-mkp .ygrps-yiv-187547347yiv2892874967ad {
padding:0 0;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967ygrp-mkp .ygrps-yiv-187547347yiv2892874967ad p {
margin:0;}

#ygrps-yiv-187547347 #ygrps-yiv-187547347yiv2892874967 #ygrps-yiv-187547347yiv2892874967ygrp-mkp .ygrps-yiv-187547347yiv2892874967ad a {
color:#0000ff;text-decoration:none;}
#ygrps-yiv-187547347



All custom fields ShortChar, Characer, NUmber etc.. if they are in use they are copied over to the Extended UD if they are null then they will be removed.


Jose C Gomez
Software Engineer



T: 904.469.1524 mobile

Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 10:06 AM, Ted Koch tkoch77@... [vantage] <vantage@yahoogroups.com> wrote:
  
<div>
  
  
  <div style="color:#000;background-color:#fff;font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:8pt;"><div><span>I have a call open with support where I had an issue migrating from E9 to E10.</span></div>

During the UD fields migration it was throwing an error on tables that I had extended using the Extended UD Table Maintenance. The extended table fields never get “copied” over.


If I delete the Extended UD tables in the maintenance window and then migrate I get no errors, but the fields obviously don’t get copied.

From: "Jose Gomez jose@... [vantage]" <vantage@yahoogroups.com>

To: Vantage <vantage@yahoogroups.com>
Sent: Tuesday, June 17, 2014 9:12 AM

Subject: Re: [Vantage] Best Practices for UD Field Reference




Also on the for what is worth category if you are in 9.05.XX I recommend you use the custom UD fields and not the standard CHaracterXX 
1) It gives you ability to know the name of the field as you had intended it vs CharacterXX
  1. In E10 all the CharacterXX fields go away in favor of the new style. So if you already have them there you are ahead of the curve


Jose C Gomez

Software Engineer


T: 904.469.1524 mobile


Quis custodiet ipsos custodes?


On Tue, Jun 17, 2014 at 8:58 AM, 'Terry M. Hall' THALL@... [vantage] <vantage@yahoogroups.com> wrote:
  
<div>
  
  
  <div>Hi,

We use the Extended Property Maintenance screen. Fill in the Label name with a description of the UD field. We also put a unique prefix in the description field and use that to filter a dashboard.

[Users:PUBLIC:Advertising:LOGO TYPES:VECTOR LOGO ADS.ai]

Terrance Hall | Techincal Support Supervisor




Thall@...<mailto:jboll@...> | [P] 563.583.7311, Ext. 5247 [F] 800.832.9296
More than a brand. We’re a family.

CONFIDENTIALITY NOTICE:
This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Tuesday, June 17, 2014 7:51 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Best Practices for UD Field Reference




Looking for suggestions in some best practices or ways you all keep track of the UD fields and tables you’ve utilized. Typically UD fields have a presence on program UIs so it’s been useful to keep track of customization change logs but it’s not infallible. Any advice for someone doing an implementation and wanting to start it out right?




Thanks,



Kyle


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

</div>
 


<div style="color:#fff;min-height:0;"></div>






</div>
 


<div style="color:#fff;min-height:0;"></div>