iwpt_dcr_values with spaces in dct names

System

Not sure if this is an issue, I have a Perl script that is reading a dcr that has names with spaces.

For example:
$Primary = iwpt_dcr_value('CurrentDCR.Interest Rate Data.Primary Credit Rate');

Wasnt it said that that spaces in dct field names are discouraged and should include under scores such as first_name instead of first name?
(I didnt design this dct to begin with).

Is the spaces in names an issue, or is there a way in Perl to ignore the spaces in the names?

If this is not an issue, then it might be something else - need to start somewhere in my trouble shooting. First extracted value comes out fine (which is a one word dct field name), but the 2nd and 3rd values do not (which have multiple word dct field names).

Thanks

TS 6.7.1, Win

Adam Stoller

Not sure if this is an issue, I have a Perl script that is reading a dcr that has names with spaces. For example: $Primary = iwpt_dcr_value('CurrentDCR.Interest Rate Data.Primary Credit Rate'); Wasnt it said that that spaces in dct field names are discouraged and should include under scores such as first_name instead of first name? (I didnt design this dct to begin with). Is the spaces in names an issue, or is there a way in Perl to ignore the spaces in the names? If this is not an issue, then it might be something else - need to start somewhere in my trouble shooting. First extracted value comes out fine (which is a one word dct field name), but the 2nd and 3rd values do not (which have multiple word dct field names). Thanks TS 6.7.1, Win

Is this an "xml" or "iwov" style DCT? If "iwov" style, it might work. If "xml" style, it is likely to cause grief.

In either case - it might be worth the effort to code up a script to fix the DCTs, DCRs, PTs, and FormAPI code to alleviate the problem now and in the future.

It takes a bit of work, and it's not 100% fool-proof (more likely to find issues in FormAPI than elsewhere as there may be things like

...getName().replace(/foo/, "bar");

- but you can usually debug those reasonably easily after the fact).

Things to consider in writing such a utility:

It's best developing this on a DEV server or DEV branch where you can create a "before" edition, and restore the contents of the workarea after each run as you debug the overall process.Is it worth it? I think so - but you may be able to fix your immediate problem in some other way and thus avoid the time it takes to develop the utility for fixing things.