Unsuported Fields When Running Custom Reports

Welcome to the Calyx Software Message Boards where you can share ideas and solutions with other Calyx users! Calyx personnel including Tech Support, Development, QA, and Business Planning often visit these message boards unofficially to better understand our customers' needs. To submit your suggestions Click Here.

This discussion forum is a service provided by Calyx Software. Calyx Software does not endorse any particular point of view expressed in this forum or any information provided in it. The use of the information provided by other users in this message board is at your own risk.

Calyx Software Message Board

Home

Members

Calendar

Who's On

Welcome Guest ( Login | Register )

Unsuported Fields When Running Custom Reports...

Rate Topic

Display Mode

Topic Options

Author

Message

heather

Posted 4/13/2007 1:32:19 PM

Forum Newbie

Group: Forum Members
Last Login: 4/16/2007 3:40:26 PM
Posts: 2, Visits: 2

I am trying to run a custom report for our loan log, and some of the fields that I try to draw information from is returned to me with an error message that reads "Warning: one or more requested fields are not currently supported by the Point Data Server (PDS)" and then it lists the fields. How can I fix this so that I can have the fields required to complete my loan log.

Heather

Post #4866

BetaFisch

Posted 4/13/2007 1:45:45 PM

Sepal

Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261

If your not using the all your additional fields you can ask your pds Administrator to add the Fields you need. Also if you want to list them here they maybe included in PDS in some future version.

Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post. Crazy

Post #4867

Bryan Telford

Posted 4/13/2007 9:00:13 PM

Supreme Being

Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901

Which field ID's are showing as unsupported?

Bryan
Point Product Manager

Post #4869

heather

Posted 4/16/2007 3:43:04 PM

Forum Newbie

Group: Forum Members
Last Login: 4/16/2007 3:40:26 PM
Posts: 2, Visits: 2

1222

2123

7300

7301

20554 (custom)

1508

20555 (custom)

339

384

25004 (custom)

983

4048

Post #4892

Bryan Telford

Posted 4/16/2007 3:51:07 PM

Supreme Being

Group: Moderators
Last Login: 12/21/2008 11:16:31 PM
Posts: 837, Visits: 1,901

For the custom fields, open your fieldid.brw file (Go to Utilities > Load Field ID > Borrower) and check the field ID's. All the custom fields should be in the 9900-9999 range. All the custom fields are supported

.For the other fields, please check with the person who administers your Point Data Server and see if they can those to the Additional Fields list.

Bryan
Point Product Manager

Post #4893

mwm50

Posted 5/9/2007 8:24:25 AM

Supreme Being

Group: Forum Members
Last Login: 9/12/2008 11:24:50 AM
Posts: 289, Visits: 242

I have found that the fields in the 20000 range don't return "real" data. They're usually calculated fields or "mirror" fields. The fieldID.brw doesn't always show the ID of the underlying field (as stored in the Point file). To find the correct field ID for some of these fields, I have had to compare two Point files that are identical except for the field I am looking for and use the field indicated in the file. That has worked for me every time.

- Mike
mike@mtig.biz

Post #5099

cbannister

Posted 11/1/2007 9:08:31 AM

Junior Member

Group: Forum Members
Last Login: 11/2/2007 8:28:07 AM
Posts: 10, Visits: 15

A client of mine is also running a custom report and getting the same response. I have checked the Additional Fields interface in PDS and they are there. I also believe that they have used these fields in previous reports. The fields we are using are 5032 to 5037.

Below is an error report.

Warning:

System.FormatException: Input string was not in a correct format.

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider

provider)

at System.Convert.ToInt32(Object value)

at System.Data.Common.Int32Storage.Set(Int32 record, Object value)

at System.Data.DataColumn.set_Item(Int32 record, Object value)Couldn't store <> in CB Experian Column. Expected type is Int32.

This message is likely the result of requesting unsupported fields from a PDS data folder.

Warning:

System.FormatException: Input string was not in a correct format.

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider

provider)

at System.Convert.ToInt32(Object value)

at System.Data.Common.Int32Storage.Set(Int32 record, Object value)

at System.Data.DataColumn.set_Item(Int32 record, Object value)Couldn't store <> in CB Equifax Column. Expected type is Int32.

This message is likely the result of requesting unsupported fields from a PDS data folder.

Warning:

System.FormatException: Input string was not in a correct format.

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider

provider)

at System.Convert.ToInt32(Object value)

at System.Data.Common.Int32Storage.Set(Int32 record, Object value)

at System.Data.DataColumn.set_Item(Int32 record, Object value)Couldn't store <> in CB Tu Column. Expected type is Int32.

This message is likely the result of requesting unsupported fields from a PDS data folder.

Warning:

System.FormatException: Input string was not in a correct format.

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider

provider)

at System.Convert.ToInt32(Object value)

at System.Data.Common.Int32Storage.Set(Int32 record, Object value)

at System.Data.DataColumn.set_Item(Int32 record, Object value)Couldn't store <> in B Experian Column. Expected type is Int32.

This message is likely the result of requesting unsupported fields from a PDS data folder.

Warning:

System.FormatException: Input string was not in a correct format.

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider

provider)

at System.Convert.ToInt32(Object value)

at System.Data.Common.Int32Storage.Set(Int32 record, Object value)

at System.Data.DataColumn.set_Item(Int32 record, Object value)Couldn't store <> in B TU Column. Expected type is Int32.

This message is likely the result of requesting unsupported fields from a PDS data folder.

Warning:

System.FormatException: Input string was not in a correct format.

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at System.String.System.IConvertible.ToInt32(IFormatProvider

provider)

at System.Convert.ToInt32(Object value)

at System.Data.Common.Int32Storage.Set(Int32 record, Object value)

at System.Data.DataColumn.set_Item(Int32 record, Object value)Couldn't store <> in B Equifax Column. Expected type is Int32.

This message is likely the result of requesting unsupported fields from a PDS data folder.

Post #6147

BetaFisch

Posted 11/1/2007 10:19:14 AM

Sepal

Group: Moderators
Last Login: Today @ 4:06:35 PM
Posts: 1,183, Visits: 9,261

You will need to remove the fields from additional/custom and re add them. then resync all the files.

Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post. Crazy

Post #6148

cbannister

Posted 11/2/2007 8:29:07 AM

Junior Member

Group: Forum Members
Last Login: 11/2/2007 8:28:07 AM
Posts: 10, Visits: 15

BetaFisch (11/1/2007)

You will need to remove the fields from additional/custom and re add them. then resync all the files.

Thanks, that resolved my issue. w00t

Post #6151

BetaFisch

Posted 11/2/2007 9:01:36 AM