Task "task outcome" field in non-english SP installation

hi guys,
I'm developing solution in english language enviroment and then install it in non-english production enviroment. And I'm having a problem with task items in sharepoint 2013 workflow. If I programmatically define TaskOutcome field value as "Approved",
in workflow If activity it doesn't have the same value as Approved.
Is there any system values for task lists or something?

I just deploy WSP file on a server.
There's no error as it is: condition in workflow looks like this:
"if outcome_1==0" (outcome_1 is a result of a single task activity)
If I open task in a default task edit form it works just fine. But if I try to complete task programmatically then I need to set task fileds values in the languege current Sharepoint install is. So following code is no good any more:
//Completing a task
var item = SPContext.Current.Item;
item["TaskOutcome"] = "Approved";
item["PercentComplete"] = "1";
item["Status"] = "Completed";
item.Update();
instead of "Approved" and "Completed" have to be words in different language.
So the question is how to set this values for all languages?

Similar Messages

Formatting non-English Characters in Database Extracts

Hi
I am trying to create data flat file with Oracle SQL extracts. The data file is position based i.e. Position 1-30 for First Name, 31-50 for Last name, etc. I encountered problems when the data fields contain non-English characters. The position shift right by 1 with every non-English characters. For example, if there is one Spanish char in First Name, Last Name will start from 32, instead of 31. If there are two Spanish chars, Last Name will start from 33 (shift 2). Is there any way, in a database session, to restrict the formats of these text fields such that non-English characters will not affect the data field position in the flat files?
Thanks in advance
Jason

An alternative might be to tab or comma delimit your data.
Eric

Task Outcome Field - Crawled Property not created

Hi,
SharePoint is not creating crawled property for the OOB Task Outcome
field... Is this by design or is it possible to include this field in search..
Regards,
Muthukumar

Hi Muthukumar,
Per my knowledge, there is not an OOB way to create a crawled property for Task Outcome field.
As a workaround, you can try to create a new column in the tasks list, then create an Event Recevier on the tasks list to handle the item is added or updated. In the Event Recevier, sest the new column to the Task Outcome. After that, do a full crawl to
find the crawled property for the new column, and use the new column instead of Task Outcome.
More information about creating Event Recevier, please refer to the link:
http://onceinawhilescribble.blogspot.com/2013/05/creating-simple-event-receiver-in.html
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Problem with Non-English Fields Output to PDF by JASPER in JDev10.1.3

I am using jsprx files(designed in i-report) to generate pdf reports out of an oracle database.
The non-English fields are shown correctly when I output the report into an HTML or when I view it with JasperView.
If I try making PDF files (JasperExportManager.exportReportToPdfFile) the static fields containing e.g.Arabic/Chineese characters won't be displayed and dynamic fields from the database with non-English contents will be shown as ??? or null.
I received some suggestions about using PARAMETERS to feed the report instead of FIELDS, which I think can not be helpful in this case and in general.
I think this should be a common problem. These are the components I am using:
itext-1.4.7. jar
commons-digester- 1.7.zip
jasperreports- 1.2.8.jar
Any comment or help is appreciated.
Thanks
Farbod

I am using jsprx files(designed in i-report) to generate pdf reports out of an oracle database.
The non-English fields are shown correctly when I output the report into an HTML or when I view it with JasperView.
If I try making PDF files (JasperExportManager.exportReportToPdfFile) the static fields containing e.g.Arabic/Chineese characters won't be displayed and dynamic fields from the database with non-English contents will be shown as ??? or null.
I received some suggestions about using PARAMETERS to feed the report instead of FIELDS, which I think can not be helpful in this case and in general.
I think this should be a common problem. These are the components I am using:
itext-1.4.7. jar
commons-digester- 1.7.zip
jasperreports- 1.2.8.jar
Any comment or help is appreciated.
Thanks
Farbod

How to validate for non-english character on a single line text field

In a "Single Line Text" field we would like to allow the users to enter alpha numeric values only. We should show error when the user enter non-English values like
carácter
Vijayaragavan, MCTS

Hi,
According to your post, my understanding is that you wanted to validate for non-english character on a single line text field.
I recommend to use jQuery to attach regular expression validation. Please refer to:
Using #jQuery to attach regular expression validation to a #SharePoint list form field
In addition, for custom validations you can create your own Types. Refer to
this[^] for creating custom field type
More information:
SharePoint Custom Field - Regex Validator
Thanks,
Linda Li
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Linda Li
TechNet Community Support

How can the symbol and non-English diacritical marking, etc accessed with combinations of letters and functional keys prior to Snow Leopard be achieved in Snow Leopard?

How can the symbol and non-English diacritical marking/punctuation pallet, available in pre-Snow Leopard OSes with various combinations of letter or number keys and functional keys, be accessed in Snow Leopard? Those pre-Snow Leopard versions worked on the fly as one was making text in any pedestrian application and its native font (Mail, Text Edit, for example). One didn't need to dig around in font libraries, change font preferences, etc.

> One didn't need to dig around in font libraries, change font
> preferences, etc.
It hasn't worked like that since the Early Chalcolithic (ie, System 7 or thereabouts).
You've already got plenty of answers. Briefly (and grossly oversimplified),
- Mac OS X conforms to a standard known as Unicode; in its current incarnation, it defines over 100k characters.
- A keypress is translated into a character according to the current keyboard layout.
- The graphic representation of a character (ie, glyph), is provided by the current font.
- If a font lacks a glyph for the requested character, either another font will be automatically chosen (Mac OS X text engine), or some form of feedback (empty box, question mark, etc) will be used.
- To inspect the actual key codes, use a utility such as Key Codes.
- To inspect the current keyboard layout, invoke Keyboard Viewer.
- To inspect the full complement of glyphs of a font, invoke Character Viewer (also accessed with the Special Characters command).
(Remember that both these utilities are resizable and zoomable -- you can enlarge them to a comfortable viewing size, then zoom out to see more of the screen for your original task.)
- For a more detailed look, use a utility such as UnicodeChecker.
- The default keyboard layout depends on your Mac OS X localisation.
(Keep in mind that there's no need to stick with the default layout; choose whichever one makes sense to you, given your language, habits, and proclivities. Mac OS X comes bundled with quite a few, including some obviously designed for the huddled masses of refugees from the Dark Side, who, in their wretched ignorance, have the unmitigated gall of labelling our native ways "really uncomfortable". Oh well, this, too, shall pass.
If none of the supplied keyboard layouts fits your needs -- if, for instance, you write your emails in Etruscan -- go out on the 'net, you'll find quite a few. Or write your own with Ukulele, it's not really all that difficult.)
- Use Keyboard Viewer to familiarise yourself with the current layout and to enter the odd character; but, to be proficient, you should learn your layout to the point that KV is no longer needed.
- Use Character Viewer to enter the odd character not available in the current keyboard layout.
Neither Keyboard Viewer nor Character Viewer are effective tools for more extensive needs, eg, for writing and editing bilingual or multilingual texts. In such a case, you should enable the respective keyboard layouts and switch between them with a keyboard shortcut.
A few interesting layouts bundled with Mac OS X have already been mentioned. Let me add three.
- Dvorak: several layouts based on the Dvorak keyboard. It is claimed that the latter is more productive and lessens RSI risk.
- US Extended: based on QWERTY, it offers a more extensive set of diacritics (eg, caron, breve) via dead keys.
- Unicode Hex Input: also based QWERTY, it allows input by Unicode codepoint (in hexadecimal), so it's the most extensive layout of all; eg, to enter the character "Parenthesized Number Twelve" (U+247F), hold down Option, type "247f", release Option.

Access to English Captivate 5 for non-English installations?

Participation in the Captivate forums is somewhat difficult when
a problem or solution description must use precise terms of Captivate 5 and when
the licensed version is non-English.
Is there an option to access or install an English version of Captivate 5 in addition to the licensed non-English version without paying twice?

Hi,
trial period is limited to 30 days - after that time? Does the English trial version accept a license key for a German version for prolongation? Is it possible to reinstall several times (at least with the license key of a non-English program version)?
The TestDrive of ADOBE eLEARNING SUITE 2 seems to be an option that may help for a few simple tasks. But I have not found a way to open any of my projects or to import preferences or styles. With those features (may be without saving capabilities) the approach would be more helpful.
So I may make use of TestDrive just to find some English terms, but I will not be able to provide screen shots of solutions or problems in an English Captivate 5 environment. Right?

How to retrieve non-english characters from a query

Hello,
My apologies if this post is not in its proper place, but I was a bit confused where to add it.
I'm running a query using SQL Developer on a table which contains several companies names from many different countries, and one of the checks I need to make to ensure data consistency is to search for all rows which the name of company contains special or non-english characters (like ç, ã, ä as example).
I don't know what can I use to do this. I tried to collate using NLS_SORT but it didn't work.
Is there someway to select only the rows that contain these special or non-english characters, excluding from the results the rows that only have english characters? Please have in mind that we have many languages in this table.
The field I would like to make the conditions on is VARCHAR2.
Please let me know if there is any extra information I should provide you so that you can help me.
Thank you in advance for the help.
Regards,
Luís

Hi Luis,
My apologies if this post is not in its proper place, but I was a bit confused where to add it.This is the Forum for the SQL Developer Data Modeler product.
I suggest you try using the SQL and PL/SQL Forum: PL/SQL
David

Cfqueryparam and non-English languages

Hi,
I want to store non-English characters in NCHAR NVARCHAR and
NTEXT field types.
In the examples below fields LastName and FirstName are
NVARCHAR type and
Comments is NTEXT
In the past when I wanted to store non English (Greek)
strings or texts in these field types I was writting

<cfquery name="Q" datasource="Db">
INSERT INTO Books
( LastName,
FirstName,
Comments )
VALUES
( N '#var_LastName#' ,
N '#var_FirstName#' ,
N '#var_Comments#' )
</cfquery>

Now I want to use the cfqueryparam, so the syntax is

<cfquery name="Q" datasource="Db">
INSERT INTO Books
( LastName,
FirstName,
Comments )
VALUES
( <cfqueryparam value="#var_LastName#"
cfsqltype="CF_SQL_VARCHAR" MaxLength="40">,
<cfqueryparam value="#var_FirstName#"
cfsqltype="CF_SQL_VARCHAR" MaxLength="30">,
<cfqueryparam value="#var_Comments#"
cfsqltype="CF_SQL_LONGVARCHAR"> )
</cfquery>

but ...... the non English characters are not stored
correctly.
So my question is
How can I use the cfqueryparam in order to store non English
characters in NCHAR NVARCHAR and NTEXT field types ???
The documentation has not any info on that.
Thank you in advance for your help
ANX
Greece

You didn't say what version of CF you were using.
Also, which database driver are you using (ODBC or JDBC
version #)?
Anyway, it looks like you do not have the unicode support
turned on. See
http://www.sustainablegis.com/blog/cfg11n/index.cfm?mode=entry&entry=F9553D86-20ED-7DEE-2A 913AFD8651643F,
etc.
If that doesn't help, post
sample data that inserts ok without cfparam but not ok with
cfparam.

Customized Skins in Non-English Projects

I have a customized skin that when used non-English projects,
it omits special characters in the buttons for Contents and Index.
I didn't create the skin so I don't have Flash. Any suggestions on
how to fix the buttons to display the missing characters?

If she's no longer with the company and she was using Flash,
could it by chance be a company license for Flash that you could
take over...?
Rick referred to the LNG file, which exists in both the
source files and the output files. Do the copying and pasting with
the source versions. (The output version will be overwritten from
the source version every time.)
If Rick's suggestion doesn't work, the only other thing I can
think of would be to check the .fla files themselves in Flash. The
person who tweaked the files may have done something to the dynamic
text fields for the button labels. If you can get a copy of Flash,
you could check two things on the button label text field
(double-click the Label object twice to get to this point):
1. See if "Use device fonts" is selected in a dropdown on the
left side of the Properties panel. This selection won't let you
embed fonts. If it's selected, try #2 below instead. If it isn't,
select it, export the movie, and put it in your output files.
2. Change "Use device fonts" to "Anti-alias for animation."
Click the Embed button. Select every option with Latin in it, and
click OK. Export to a movie, and put it in your output files.
Note that you'd have to do this for each button that isn't
displaying the characters properly.
Hope this helps,
Ben

Themes in non-English

Curious...All the themes are in non-English when I preview them. I didn't change any settings that I'm aware of. Is that normal?

If you are talking about the latin text in the fields and titles, that is normal for english. They expect you to replace that example text with your own.

Non english characters in bi problem

dear all,
i have problem with non English chars in bw. in r3 side my client uses non English chars which is allowed, however when i get data to bw side it gives error when i see psa , i see records which has # in it, leads to error.
example : wbs element.
any help for that? i have checked customizing in spro about non English chars.
thanks in advance.

Hi,
Try RSKC --> type ALL_CAPITAL --> F8 (Execute)
OR
Go to SE38 and execute the program RSKC_ALLOWED_CHAR_MAINTAIN and give ALL_CAPITAL or the char you want to add.
Check the table RSALLOWEDCHAR. It should contain ALL_CAPITAL or the char you have entered.
As a long term you can apply some user exit in source system side or change your update rules to ensure that this field is getting blanked out before getting loaded in cube or add that particular char to permitted character list in BW.
Refer
/people/sap.user72/blog/2006/07/23/invalid-characters-in-sap-bw-3x-myths-and-reality-part-2
/people/sap.user72/blog/2006/07/08/invalid-characters-in-sap-bw-3x-myths-and-reality-part-1
/people/aaron.wang3/blog/2007/09/03/steps-of-including-one-special-characters-into-permitted-ones-in-bi
http://help.sap.com/saphelp_nw04/helpdata/en/64/e90da7a60f11d2a97100a0c9449261/frameset.htm
For adding Other characters
OSS note #173241 u2013 u201CAllowed characters in the BW Systemu201D
Sample cleansing routine (#)
Help loading char EQUIP#1111#TAG#3311 SN#A01040 * into Cube
Thanks,
JituK

Formula to show non english characters from clob in crystal report

Hi
I am using the database Oracle 11g with a field clob in one of the table that i want to show in the crystal report
But the problem is when i put the clob field in crystal report it is outputting the results perfectly for English characters but not for the Arabic ones and returning the string like (¿¿¿¿ ¿¿¿¿ ¿¿¿ ¿¿¿¿ ¿¿¿¿ ¿¿¿ ¿ ¿¿¿¿¿ ¿¿¿)
so is there any way to show the arabic (non english) characters perfectly on crystal report with clob field

Hi Azeem,
Make sure the arabic font should install in your system.
Try this:
Create a text field in your Crystal Report (a label).
Place Arabic characters into that field (just by typing them into it on the report definition).
Run the report. If they display correctly then its probably not Crystal, but rather would point to an issue in the data retrieval and supply to Crystal via your dataset (or whatever datasource you are using).
If they don't display - then its definitely Crystal.

Non English characters conversion issue in LSMW BAPI Inbound IDOCs

Hi Experts,
We have some fields in customer master LSMW data load program which can
contain non-English characters. We are facing issues in LSMW BAPI
method with non-English characters Conversion. LMSW steps read and
conversion are showing the non-English characters properly with out any
issue. While creating inbound IDOCs most of the non-English characters
replaced with '#' and its causing issues in creating customer master data in
system. In our scenario customer data with non-English characters in
the first name, last name and address details. Any specific setting
needs to be done from our side? Please suggest me to resolve this issue.
Thanks
Rajesh Yadla

If your language is a unicode tehn you need to change the options like IN SAP you need to change it to unicode in the initial screen Customize local layout(ALT F12) options 118 --> Encoding ....

Entry of non-English characters into the db

Hi
We are facing a problem in inserting non-English characters into the database.For example, we have a company name field which can accept German characters. This field has been defined as of varchar2 type of size 50 in the db. When we enter 49 English characters and then one German character, the database is throwing the error that the inserted value is too large for the column.Is it that the German character is taken as equivalent to two English characters ? Or is there any database level setting that can be done for this ? For the time being we have identified certain critical fields and have doubled the size of their fields in the db. But I guess there has to be another solution to this....
Please help.
null

Indeed, your German character is using two bytes to store itself. Consult the Oracle JDBC Developer's Guide.
null

Task "task outcome" field in non-english SP installation

Similar Messages

Maybe you are looking for