AS_STRING problem

bartthefish

Hi, I've got a major problem.

The AS_STRING function used to work beautifully, but now it has gone mad.

Let me explain. I need to export to a .TXT file a numeric value for an external app. The external app needs the value to come in the following format '0000000000000' so if the product value is $ 10 000.00 then the export needs to be '0000001000000'

My Rule is as follows:

BO.ExportTXT=Product.Name+'~'+PAD_LEFT(REPLACE_PATTERN(AS_STRING(Product.Value*100),'.0',''),'0',13)

This used to work beautifully but now the export returns '000000001.E87' instead.

Please can someone help me as this is extremely urgent

Thanks

P.S. This is on v4.7

aware_support

Your Product.Value must be crazy in this particular case. There is no other explanation. Check the value of this attribute.

bartthefish

I've double checked the value in the Database.

The field is correctly configured as type 'float' The value's are correctly stored as 10000.00 for eg. in the DB. It is definitely when the value is converted to a string that the error occurs.

I am currently testing this problem on other machines as well, so far it has the same outcome.

bartthefish

(Please note that in the posts above the values represented are not the exact values where the problem occurs. As you will see my lack of clarity might have added to the confusion. I hope this post will clear up any such confusion)

I've narrowed the problem and it occurs even on v4.8 Build 1280.
As soon as the number to be converted to a string is greater that 9 999 999 the problem occurs.

The big problem is that the values I'm dealing with are most often much greater that this.

To replicate this:
Create a BO with two fields
Value of Type = 'Number'
Display of Type = 'Plain Text'

Then create a rule:

IF BO.Value WAS CHANGED THEN BO.Display=AS_STRING(BO.Value)

You can make this dynamic to see immediately.

aware_support

How is the format for the number defined?

bartthefish

The number is formated as 0000000000000 with initial value of 0000000000000

Hmm...Never thought to look at that. Due to the fact that the user doesn't need to see this value I might be able to change the formating to be # instead.

It seems that if the Database field is of type Float the problem occurs, but when it is set as BigInt it is not a problem.

Will test now, and let you know how it goes

bartthefish

It appears whilst changing the formatting of this to # (big int) the conversion to string is still a problem

As an example a value of 147200 should be converted to 0000014270000 but is instead converted to 0000000001470

Please help

bartthefish

Sorry. By removing the REPLACE_PATTERN (Which is no longer necessary the dropping of the trailing zero's no longer happens)

I is amazing how a simple question like

How is the format for the number defined?

can set the wheels turning and the problem can be solved

Thanks for your quick response