I have custom field with input text. I have added arabic language support in control panel
but when I insert an arabic word it says Users and Organizations is temporarily unavailable.
How to solve this issue?
This is what happened in console log:
10:29:49,421 ERROR [http-bio-8080-exec-17][JDBCExceptionReporter:82] Incorrect string value: '\xD8\xB9\xD8\xB1\xD8\xA8...' for column 'data_' at row 1
10:29:51,254 ERROR [http-bio-8080-exec-17][render_portlet_jsp:132] null
java.sql.SQLException: Incorrect string value: '\xD8\xB9\xD8\xB1\xD8\xA8...' for column 'data_' at row 1
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4120)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4052)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2503)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2664)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2794)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2458)
at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2006)
at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1135)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:70)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:268)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:114)
at org.hibernate.jdbc.AbstractBatcher.prepareStatement(AbstractBatcher.java:109)
at org.hibernate.jdbc.AbstractBatcher.prepareBatchStatement(AbstractBatcher.java:244)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2412)
at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2875)
at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:79)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:273)
Take a look at http://www.codeka.com.au/blog/2014/02/unicode-support-in-mysql-is--
and https://news.ycombinator.com/item?id=7317519.
Basically it is because of the incorrect character encoding set for your database.
Related
enter image description here
select from list by index ${locator_var} ${inp_msge_type}
--getting error as expected string, int found
select from list by index ${locator_var} 7
-----not getting any error
${inp_msge_type}----contains 7 from DB query the result is stored in this variable, to avoid hard coding we need to do this
Is there any way to write
Do not add links to screenshots of code, or error messages, and format the code pieces accordingly - use the ` (tick) symbol to surround them.
The rant now behind us, your issue is that the keyword Select From List By Index expects the type of the index argument to be a string.
When you called it
Select From List By Index ${locator_var} 7
, that "7" is actually a string (though it looks like a number), because this is what the framework defaults to on any typed text. And so it works.
When you get the value from the DB, it is of the type that the DB stores it with; and probably the table schema says it is int. So now you pass an int to the keyword - and it fails.
The fix is simple - just cast (convert) the variable to a string type:
${inp_msge_type}= Convert To String ${inp_msge_type}
, and now you can call the keyword as you did before.
In the SO Invoice report, I add a link from ARTran to FSAppointment. This is done in order to include FSappointment.LongDescr in the report. A request, is to remove the text 'Internal Notes' PLUS all text following the string. I notice a red error message printed in the report output, in the cases where 'Internal Notes' string is not included in LongDescr. I tried several permutations but have not found a resolution.
Here is my formula
=IIf(InStr([FSAppointment.DescriptionAsPlainText],'Internal Notes')>0,
Left( [FSAppointment.DescriptionAsPlainText], InStr([FSAppointment.DescriptionAsPlainText],'Internal Notes') )
,[FSAppointment.DescriptionAsPlainText])
Note that I created a non-bound field DescriptionAsPlainText, in order to apply pretty formatting, for LongDescr field.
Here is the error message:
An error has occurred while the Left(Identifier(FSAppointment.DescriptionAsPlainText), InStr(Identifier(FSAppointment.DescriptionAsPlainText), Const(Internal Notes))) function was being executed:
'Length cannot be less than zero.
Parameter name: length'
I think your code fails if the value of [FSAppointment.DescriptionAsPlainText] is null. Add an IIF([FSAppointment.DescriptionAsPlainText]=null, clause around your existing code to exit in case of null.
I am using python SDK version 3.3 and I am trying to place tabs using anchor string. My use case is sending multiple documents through a single envelope to multiple recipients.
For recipient 1, the anchor string in document 1 is (let us say) “Sign here” and anchor string in document 2 is “Assessee”.
For recipient 2, the anchor string in document 2 is “Sign here”.
Now when I am anchoring tabs, I am passing the recipient id , document id and the anchor string, I even tried by parsing the page number. Docusign seems to be searching for anchor string across all the documents.
For example: I get a error message saying “Assessee” is not found, but I specifically mentioned "Assessee" for document 2. What am I missing here? Please help
----- Snippet -----
sign_here1 = docusign.SignHere(anchor_string='Sign here',
recipient_id='1',
document_id= '1',
anchor_units='inches',
anchor_y_offset='0.6',
anchor_x_offset='0.5',
anchor_ignore_if_not_present=False
)
sign_here2 = docusign.SignHere(anchor_string='Assessee',
recipient_id='1',
document_id= '2',
anchor_units='inches',
anchor_y_offset='0.6',
anchor_x_offset='0.5',
anchor_ignore_if_not_present=False
)
sign_here3 = docusign.SignHere(anchor_string='Sign here: ',
recipient_id='2',
document_id= '2',
anchor_units='inches',
anchor_y_offset='0.6',
anchor_x_offset='0.5',
anchor_ignore_if_not_present=False
)
----- Error message -----
"errorCode":"ANCHOR_TAB_STRING_NOT_FOUND","message":"The specified Anchor Tab string was not found in the document. Anchor Tab String \"Assessee\" not found."This is the output, I recieve. But I have mentioned only document_id '2' in sign_here2
Your code has :
anchor_string='Assessee'
This means DocuSign scans the document and looks for this word. If the word cannot be found - this tab cannot be placed.
The idea of an anchor string is to find how to place the tab based on some text, a few characters, a word or something in the document.
Since, you also have x_position and y_position, maybe you misunderstood how tab positioning work? you typically have one or the other.
there's an offset you can use for the anchor, but that's different that x_position.
Try to just remove the anchor_string and see what happens.
I'm getting this message in Redshift: invalid input syntax for type numeric: " " , even after trying to implement the advice found in SO.
I am trying to convert text to number.
In my inner join, I try to make sure that the text being processed is first converted to null when there is an empty string, like so:
nullif(trim(atl.original_pricev::text),'') as original_price
... I noticed from a related post on coalesce that you have to convert the value to text before you can try and nullif it.
Then in the outer join, I test to see that there's a limited set of acceptable characters and if this test is met I try to do the to_number conversion:
,case
when regexp_instr(trim(atl.original_price),'[^0-9.$,]')=0
then to_number(atl.original_price,'FM999999999D00')
else null
end as original_price2
At this point I get the above error and unfortunately I can't see the details in datagrip to get the offending value.
So my questions are:
I notice that there is an empty space in my error message:
invalid input syntax for type numeric: " " . Does this error have the exact same meaning as
invalid input syntax for type numeric:'' which is what I see in similar posts??
Of course: what am I doing wrong?
Thanks!
It's hard to know for sure without some data and the complete code to try and reproduce the example, but as some have mentioned in the comments the most likely cause is the to_number() function you are using.
In the earlier code fragment you are converting original_price to text (string) and then substituting an empty string ('') if the value is NULL. Calling the to_number() function on an empty string will give you the error described.
Without the full SQL statement it's not clear why you're putting the nullif() function around the original_price in the "inner join" or how whether the CASE statement is really in an outer join clause or one of the columns returned by the query. However you could perhaps alter the nullif() to substitute a value that can be converted to a number e.g. '0.00' instead of ''.
Sorry I couldn't share real data. I spent the weekend testing small sets to try and trap the error. I found that the error was caused by the input string having no numbers, which is permitted by my regex filter:
when regexp_instr(trim(atl.original_price),'[^0-9.$,]') .
I wrongly expected that a non numeric string like "$" would evaluate to NULL and then the to_number function would = NULL . But from experimenting it seems that it needs at least one number somewhere in the string. Otherwise it reduces the string argument to an empty string prior to running the to_number formatting and chokes.
For example select to_number(trim('$1'::text),'FM999999999999D00') will evaluate to 1 but select to_number(trim('$A'::text),'FM999999999999D00') will throw the empty string error.
My fix was to add an additional regex to my initial filter:
and regexp_instr(atl.original_price2,'[0-9]')>0 .
This ensures that at least one number will be in the string and after that the empty string error went away.
Hope my learning experience helps someone else.
Yesterday, I noticed something odd when returning a varchar(100) output parameter from my stored procedure in my asp.net application. It appears that the returned value is now including the extra white spaces to return a full 100 characters. This behavior is new. The only thing I have changed recently is migrating the project from VS 2015 to 2017. I am using System.Data.SQLClient to connect to the database. Select statements for varchar columns return just the values in the columns and no extra white spaces. Ansi_padding is off for the database and is not set any where in the code.
set #Message = 'Project Updated!' --where #Message is varchar(100)
This will return to the client.
_UpdateStatus = oData.outputParams.Item("#Message")
_UpdateStatus = "Project Updated! "
Any ideas as to what is happening?
Lazy solution:
_UpdateStatus = ((string)oData.outputParams.Item("#Message")).Trim()