Why does & in text input turn into &

BLOMASKY

This has been happening more and more, so I assume something has changed in V10 (or perhaps V9). When the user enters an & in a text field, it turns into &. I do not have HTML input. These are just plain old text fields that print on invoices / statements and confuses the customer.

Bruce

aware_support3

BLOMASKY
Could you provide a small BSV for us to take a look please.

kklosson

I’ve seen other problems with this so I use REPLACE_PATTERN([value],‘&’,‘and’) as needed.

Jaymer

I think v10 is fucking up all our data - and its been happening 8-9 days for us.

I have a part where the description is: pipe 12″ × 1″
and when it prints in the report writer its F-d up

Below, see the ItemDesc field. Its coming into from the web post with the " replaced (which is correct, it has to)

Got XML request <root><post_form_data_action object_name="ServiceCodes" object_id="2027173" object_version="2" form_name="SvcCodeDetails" form_context="edit" screen_width="2326" screen_height="1013" screen_orientation="landscape" > 
<post_attribute_data attribute_name="ItemType" >2</post_attribute_data> 
<post_attribute_data attribute_name="ItemCode" >test</post_attribute_data> 
<post_attribute_data attribute_name="ItemDesc" >pipe 12&quot; x 1&quot;</post_attribute_data> 
</post_form_data_action>

But before upgrade 10 days ago, it used to be stored in the DB just fine.
This image is sorted by BASTIMESTAMP. Recent ones since upgrade are fubar.
(except for the 2nd line, all these are the same Item.

Jaymer

Now customers are seeing this on a quote/receipt/invoice.

The items in inventory look fine, and if I edit one, it does not mess up the description, NOR save the ‘quot’ stuff in the DB.

Jaymer

This shows how items were getting stored into our sales line item file, before/after upgrade over the weekend of the 10th

some items didnt use " for inches , so they are fine.
others print exactly what you see on the order PDFs and Emails to customers

I mean i COULD HAVE done something wrong somewhere that changed this behavior, but what?
Is there something in the release notes for this ?
I’m not even sure how to fix it.

BLOMASKY

Jaymer
You can easily fix it via a SQL replace statement. Happy to help you.

BLOMASKY

There is NO BSV. I have a LARGE BSV and just like JAYMER said and KKLOSSON said, when either an & or a ' or " is entered into a text field, it turns into the & It’s a bug and you should be able to figure it out.

Can’t you duplicate it?
Thank you

Bruce

aware_support3

BLOMASKY It’s a bug and you should be able to figure it out.

Can’t you duplicate it?

Not if we don’t know the steps that you’ve taken that result in that output.

We can’t divert resources to an unguided bug hunt.

Jaymer

I think I proved that the error started once we were running under version 10.
That was just from one data file on a particular item code.

I’m sure I could find many other instances in the line item file where the code is suddenly appearing after the upgrade.

What I find interesting, and I might’ve wrote about this already, is that if I edit a part, including one of these characters that has to be escaped, that it is getting stored in the database just like we would expect.

But when that table is a detail table that references the line item by part number, and is brought in and saved in the table, then it garbles the data.

In one of my cases, if we enter part “ABC“ adding the line item, we enable the editing of the description field Locally that gets saved in the line item file.
So something is different between saving that, and just editing the inventory master and saving that, where it correctly saves the double quote.

Jaymer

There are still lots of weird things happening in version 10, but I am surprised are still not fixed. It’s almost like no one is using version 10.
I mean there were a ton of bugs in the change log
And doesn’t everybody complain about this larger font thing that makes the system go totally wonky. I already wrote this up.
Is nobody using larger fonts on windows.
Inversion nine and eight, the way the CSS was injected into the config tool, while cumbersome, made complete sense and was pretty simple.
And it changed your font size. Easy. And it worked.
Now, with larger fonts, I still have to squint and enlarge my screen just to see my rules in textual view.
How could this not be fixed yet?

aware_support

We have just run a small test that creates an object with a text attribute. We entered the following values:
I12″ × 1″ (Using quotation marks). And after that : 1&2 (Using an ampersand).
In all scenarios AwareIM behaved properly. If there is a bug, please help us reproduce it. If Jaymer or Bruce could produce a small BSV with a text attribute and specific values you use, it would go a long way to fixing the issue quickly.
About larger fonts - I don’t think there were any changes in version 10 that could have affected this. What exactly are you doing there, Jaymer?

Jaymer

aware_support
yes, if you edit an object from a grid and then a form to edit, it saves correctly.

But in a Line Item scenario, when I reference that same record, and copy that description into the line item table I see it with “"” text.
I just saw this in action over the weekend, so now I know how to duplicate it, and will try something in the CRM

Jaymer

aware_support if I return to the original size font, and never select “larger fonts“ in the config tool settings, dialogue, then 100% of these issues go away.
There’s no screen jitter, there’s no problem saving, I don’t have to save twice, when I click on a X to close a tab, it doesn’t ignore it,… So if you’ve never clicked larger settings, you’ve never seen this problem, but tons of issues when you’re in larger mode.

Jaymer

Windows (not Mac)
I just set the Large option in the new Settings dialog.
Rules text stays small.
And if you edit Applicability on a Grid ROW Operation (to name one example) , the text inside there is small.
And Eclipse acts weird as hell - will have to make a video.

nhofkes

Jaymer, in your earlier post you wrote that you are having the “larger fonts” issue when working on Windows. But it seems that this settings is not supposed to be used on Windows, only on Macs. At least that’s what I see in my Config Tool settings (v10 build 3529):