Table field quirk

2015-08-10 Thread Ingrey, Rosemary
Hi all,

I'm wondering if anyone else has come across this, and if there's a workaround?

Using Remedy 8.1.02

I have a cell based table on a form which already has a considerable number of 
columns which are used in workflow.

I've added two new fields to the form it queries, however these aren't 
available for selection from the field list.

This happened previously when the table wasn't so large so I reselected the 
Form, losing all the columns, and then added them back with the correct 
database names and IDs.

I'd prefer not to do this again, however. Is there a way to avoid it?

Thanks & regards,
Rosemary

This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure. You should immediately delete the message 
if you are not the intended recipient. If you have received this email by 
mistake please delete it from your system; you should not copy the message or 
disclose its content to anyone. 

This electronic communication may contain general financial product advice but 
should not be relied upon or construed as a recommendation of any financial 
product. The information has been prepared without taking into account your 
objectives, financial situation or needs. You should consider the Product 
Disclosure Statement relating to the financial product and consult your 
financial adviser before making a decision about whether to acquire, hold or 
dispose of a financial product. 

For further details on the financial product please go to 
http://www.bt.com.au/general/rse.asp 

Past performance is not a reliable indicator of future performance.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Table field quirk

2015-08-11 Thread Grooms, Frederick W
What type and size fields did you add to the form?

Fred

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Ingrey, Rosemary
Sent: Monday, August 10, 2015 8:52 PM
To: arslist@ARSLIST.ORG
Subject: Table field quirk

**
Hi all,

I'm wondering if anyone else has come across this, and if there's a workaround?

Using Remedy 8.1.02

I have a cell based table on a form which already has a considerable number of 
columns which are used in workflow.

I've added two new fields to the form it queries, however these aren't 
available for selection from the field list.

This happened previously when the table wasn't so large so I reselected the 
Form, losing all the columns, and then added them back with the correct 
database names and IDs.

I'd prefer not to do this again, however. Is there a way to avoid it?

Thanks & regards,
Rosemary

This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure. You should immediately delete the message 
if you are not the intended recipient. If you have received this email by 
mistake please delete it from your system; you should not copy the message or 
disclose its content to anyone.

This electronic communication may contain general financial product advice but 
should not be relied upon or construed as a recommendation of any financial 
product. The information has been prepared without taking into account your 
objectives, financial situation or needs. You should consider the Product 
Disclosure Statement relating to the financial product and consult your 
financial adviser before making a decision about whether to acquire, hold or 
dispose of a financial product.

For further details on the financial product please go to 
http://www.bt.com.au/general/rse.asp

Past performance is not a reliable indicator of future performance.



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"


Re: Table field quirk

2015-08-11 Thread Ingrey, Rosemary
Good point Fred, I figured it out - I was trying to use Display Only fields, 
replaced them with Optional fields and its perfect :)

Rosemary Ingrey
Remedy Service Request Management Specialist



Group Services
Level 26, 60 Martin Place,
Sydney NSW 2000 Australia

P +61 7 4039 4260

E ring...@westpac.com.au<mailto:ring...@westpac.com.au>





[cid:image003.png@01D010A6.D6E40E30]

Noticed a job well done or an outstanding achievement? Put a 
Spark<http://cms.intranet.westpac.com.au/content/ppl/GrpServRec.nsf/Pages/SparkHome>
 into their day today!

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Grooms, Frederick W
Sent: Tuesday, 11 August 2015 11:12 PM
To: arslist@ARSLIST.ORG
Subject: Re: Table field quirk

**
What type and size fields did you add to the form?

Fred

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Ingrey, Rosemary
Sent: Monday, August 10, 2015 8:52 PM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Table field quirk

**
Hi all,

I'm wondering if anyone else has come across this, and if there's a workaround?

Using Remedy 8.1.02

I have a cell based table on a form which already has a considerable number of 
columns which are used in workflow.

I've added two new fields to the form it queries, however these aren't 
available for selection from the field list.

This happened previously when the table wasn't so large so I reselected the 
Form, losing all the columns, and then added them back with the correct 
database names and IDs.

I'd prefer not to do this again, however. Is there a way to avoid it?

Thanks & regards,
Rosemary

This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure. You should immediately delete the message 
if you are not the intended recipient. If you have received this email by 
mistake please delete it from your system; you should not copy the message or 
disclose its content to anyone.

This electronic communication may contain general financial product advice but 
should not be relied upon or construed as a recommendation of any financial 
product. The information has been prepared without taking into account your 
objectives, financial situation or needs. You should consider the Product 
Disclosure Statement relating to the financial product and consult your 
financial adviser before making a decision about whether to acquire, hold or 
dispose of a financial product.

For further details on the financial product please go to 
http://www.bt.com.au/general/rse.asp

Past performance is not a reliable indicator of future performance.


_ARSlist: "Where the Answers Are" and have been for 20 years_

This message and any attachment is confidential and may be privileged or 
otherwise protected from disclosure. You should immediately delete the message 
if you are not the intended recipient. If you have received this email by 
mistake please delete it from your system; you should not copy the message or 
disclose its content to anyone. 

This electronic communication may contain general financial product advice but 
should not be relied upon or construed as a recommendation of any financial 
product. The information has been prepared without taking into account your 
objectives, financial situation or needs. You should consider the Product 
Disclosure Statement relating to the financial product and consult your 
financial adviser before making a decision about whether to acquire, hold or 
dispose of a financial product. 

For further details on the financial product please go to 
http://www.bt.com.au/general/rse.asp 

Past performance is not a reliable indicator of future performance.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"