Hi. Hopefully I'm posting this in the right place. 
I have a report that’s based on a TTX file. CR v. 14.0.2.364 RTM. The TTX data is loaded through an ASP file and displayed through a 3rd party software. I’m kind of new-ish to this.
Here’s the problem part of the design:
The fields are, in order from left to right:
[ul]
[li]quoted unit price[/li]
[li]text box with a slash (/), followed by a space, followed by the {Price_UofM} field. The Price_UofM field was inserted in just about every way imaginable – by dragging directly from the Formula Fields list into the text box, by dragging to a new field, updating the formatting, and then dragging it into the text box, by dragging it into a new text box and then inserting the slash, by typing the slash and then dragging into the text box…
[/li]
[li]Just the Price_UofM field (for debugging purposes, to show that there’s nothing wrong with the field itself)[/li]
[/ul]
And here’s the result:
As you can see, the quoted unit price appears correctly, and the debug version of the Price_UofM field appears correctly (that’s the “ea” text), and the middle field shows the slash and the space, but there’s just a box (or maybe an empty set of brackets) where the Price_UofM inserted field should be.
I’ve run into this problem almost every single time with this field and other “unit of measure” type fields.
In the field definition file, Price_UofM is defined as “String 4 HHHX”. There is another "unit of measure"-type field, Order_Unit, that's defined exactly the same way and has the same type of data, and that also has a concatenated field in the report. And it had the exact same problem... but then I fixed it, somehow - and I have no idea how. It seemed like I was just repeating the same thing that I’d tried over and over before, and then, suddenly, it worked. But I'm getting really tired of trying that method of fixing things (just trying the same thing over and over in the hopes that it'll work THIS time), so I'd really like to know exactly how to fix it! Especially since this particular issue comes up... a lot. For the same reason, while I know that I don't have to use concatenated boxes, I really would like to, but without having to go through this every time.
Many thanks for any help you can provide!
Katie
I have a report that’s based on a TTX file. CR v. 14.0.2.364 RTM. The TTX data is loaded through an ASP file and displayed through a 3rd party software. I’m kind of new-ish to this.
Here’s the problem part of the design:
The fields are, in order from left to right:
[ul]
[li]quoted unit price[/li]
[li]text box with a slash (/), followed by a space, followed by the {Price_UofM} field. The Price_UofM field was inserted in just about every way imaginable – by dragging directly from the Formula Fields list into the text box, by dragging to a new field, updating the formatting, and then dragging it into the text box, by dragging it into a new text box and then inserting the slash, by typing the slash and then dragging into the text box…
[/li]
[li]Just the Price_UofM field (for debugging purposes, to show that there’s nothing wrong with the field itself)[/li]
[/ul]
And here’s the result:
As you can see, the quoted unit price appears correctly, and the debug version of the Price_UofM field appears correctly (that’s the “ea” text), and the middle field shows the slash and the space, but there’s just a box (or maybe an empty set of brackets) where the Price_UofM inserted field should be.
I’ve run into this problem almost every single time with this field and other “unit of measure” type fields.
In the field definition file, Price_UofM is defined as “String 4 HHHX”. There is another "unit of measure"-type field, Order_Unit, that's defined exactly the same way and has the same type of data, and that also has a concatenated field in the report. And it had the exact same problem... but then I fixed it, somehow - and I have no idea how. It seemed like I was just repeating the same thing that I’d tried over and over before, and then, suddenly, it worked. But I'm getting really tired of trying that method of fixing things (just trying the same thing over and over in the hopes that it'll work THIS time), so I'd really like to know exactly how to fix it! Especially since this particular issue comes up... a lot. For the same reason, while I know that I don't have to use concatenated boxes, I really would like to, but without having to go through this every time.
Many thanks for any help you can provide!
Katie