Difference between revisions of "Express Entry:Issues"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
[[Express Entry|← Express Entry]] | [[Express Entry|← Express Entry]] | ||
{{CustomTOC}} | |||
==GlobalExpressFreeForm Requests for Germany== | |||
When performing a GlobalExpressFreeForm request for Germany, multiple records for the same address may be returned, each with differing dependent localities. This issue may also show up in GlobalExpressPostalCode, when multiple localities are returned for a postal code. | |||
==Internet Explorer Compatibility== | |||
Internet Explorer does not properly UTF-8 encode accented characters, so it is necessary to encode diacritic characters, for example %C3%A0 for accented a. | |||
==Cached Suggestions== | |||
Cached suggestions may appear when backspacing to a number of characters below the 'MaxL' parameter (set in the sample code). | |||
==GlobalExpressAddress Address1== | |||
Addresses not starting with the search term may occur in GlobalExpressAddress when using less than 4 characters in the address1 parameter. | |||
[[Category:Web Services]] | |||
[[Category:Express Entry]] | |||
Revision as of 23:56, 17 February 2015
GlobalExpressFreeForm Requests for Germany
When performing a GlobalExpressFreeForm request for Germany, multiple records for the same address may be returned, each with differing dependent localities. This issue may also show up in GlobalExpressPostalCode, when multiple localities are returned for a postal code.
Internet Explorer Compatibility
Internet Explorer does not properly UTF-8 encode accented characters, so it is necessary to encode diacritic characters, for example %C3%A0 for accented a.
Cached Suggestions
Cached suggestions may appear when backspacing to a number of characters below the 'MaxL' parameter (set in the sample code).
GlobalExpressAddress Address1
Addresses not starting with the search term may occur in GlobalExpressAddress when using less than 4 characters in the address1 parameter.