If I type any number it should only show a default PH +63 which is Philippines default number.
Typically the default country is determined based on the browser's locale setting, e.g. topmost language in the Languages dropdown of chrome://settings/languages
For this donation flow you can also pass an lc variable with a default locale set, see https://developer.paypal.com/docs/paypal-payments-standard/integration-guide/Appx-websitestandard-htmlvariables/#paypal-checkout-page-variables
Related
Using the form InventOnHandItemto get information about available stock, in a multi-company configuration, we have remarked that the default filter (query), is not the same in the different companies.
In some companies, the form filters on the value of InventSum.Closed or on the value of InventSum.ClosedQty. In some others all data are displayed.
We have searched for parameters defining this behaviour, but we have found none. It must be programmatical : by which way can we define the default value of this filter ?
I'm writing a few profiles in fhir, and to them I've added an element with type Quantity. In the documentation it states that Quantity is like a special case of a code, where you can state the unit type/dimension of the quantity (e.g. it's a temperature, weight, length, etc).
I cannot find an example of how to add that restriction to my quantity element however, just how to specify the unit in the resource based on the profile. What's the correct way of doing this?
Simply specify a binding - you can use binding to declare the value set for the units for quantity (just as you specify one for a CodeableConcept data type)
I have the following problem.
The LogisticsPostalAddress form is displaying the StreetInKana field. (this holds special characters used in Japan". The underlying EDT extends an EDT which has 'JPN' in the CountryRegionCodes property. The company I am using has primary address with country'GBR'. My understanding is that this should mean the field would be hidden, but it is not. So far we have made very few changes to standard AX code, and nothing that would be related. So either I have set something up wrong, or these fields are meant to be displayed, which would surprise me. Any ideas?
You have to change the property CountryRegionContextField of the corresponding control to point to the field which has CountryRegionCodes value set (either on table level, or EDT level).
I guess you have to explicitly set this property because you can have different forms with the same table as data source, but restrict access only on some of them.
Need help with Google Analytics filters via Custom Reports -- Display LANGUAGE and VISITS where the LANGUAGE values are grouped as EN for each English, etc via 'FlatTable'
My report returns (see first 3 lines):
LANGUAGE | VISITS
---------+-------
en-us | 55,842
en | 3,932
en_us | 248
I would like to see:
LANGUAGE | VISITS
---------------------+----------+-------
1. en | 60,022
2. ...
3. ...
I'd recommend creating a Custom Dimension to store an extracted part from the Language Setting dimension via an Advanced Filter.
That way you will extend your data instead of replacing parts of it.
Create a Dimension LanguageCode with scope User or Session in the property's settings (Admin > Property > Custom Definitions > Custom Dimensions)
Create an advanced filter Extract Language Code in the view's filter settings (Admin > View > Filter) like so:
Field A: Language Settings ([a-z]{1,3}).*
Output in: Language (the Custom Dimension) $A1
Be aware that filters get applied during processing, which happens once a day. That means you'll be able to see the result the next day.
Then you'll be able to view reports or build a custom report that uses that new Language Code dimension.
If I'm understanding you correctly, go to Custom Reports and set one up like this:
Then, go and to the newly created report and apply a secondary dimension of Language. If you want to 'group' them by language, do a sort by Language.
I add Language to the dimension drilldown so if you were interested in seeing the possible language selection for a particular country you could do that by clicking on the country.
In Google Analytics Admin create an additional view to the property. Then create two custom filters:
Name (e.g. Language lowercase): Lowercase -> Filter Field: Language
Settings;
Name (e.g. Language generalisation): Search and Replace ->
Filter Field: Language Settings : Search string: ([a-z]{1,3})[-_]?.* Replace string: \1
That is it. Now all languages in the view will be up to 3 character long and aggregated.
Actually the regex can be more strong, but this one is more wide and covers even some wrong language settings.
I have taxonomy term with field collection field set to unlimited values. FC contains few texfield, textarea and image fields. FC and it's fields are set to be translated by user.
Taxonomy term is localized - all terms are the same for all languages just that they are translated. I have entity translation turned on for taxonomy term and node but not for FC because it trigers notice about not valid base path.
With this configuration: I create term and save it, after initial creation i can add any number of FCs and save them. On translate form I can then add translations for them. And when saved values remain saved for different laguages.
Problem occures when I create a view with relationship to FC, add FC fields and set contextual filter to termID (showing this view via panel on taxonomy terms). Field language stting is set to current user language. On views preview with manually set termID I see proper result for language in url (en/admin/structure/views..) and correct result if I change language prefix. But on term page it doesn't show anything.
I am using latest dev entiy translation an field collection modules.
I also tried setup with entity translation enabled for FC but again i don't get right output from views.
Where am I doing it wrong? FC setup, multilangual setup or in views. Does anyone have a hint how to make FC translatable?
I retested on clean installation. All this apply for what I described in #9 . Same result but some new/confirmed observations and possible workaround:
There is a bug in FC when translating fields for the first time values are not properly saved:
values are saved but when I refresh edit page, fields exist but are
empty/blank, fields on default language are ok
what really happens: when saving translation of FC fields, they are wrongfully linked to default language and not to translated one, also they don't show up when reopening default language so that they could be deleted. This can be bad if you accidentally catch them in a view as I did (for some time this was misleading me because titles were the same).
possible workaround: when first translating you have to delete values that are copied from default language and save it, then you can enter translated values
ET for FC enabled: same issue and workaround
After creating some content on terms and translating them with workaround, I tried to show them in panels via view.
I created a panel and set selection to taxonomy vocabulary I am using and under content I created "new custom content" in which I included some substitutions - for FC field %term:field_test_fc (this is my test content)
when I change language, values change accordingly to selected language
substitution renders all fields of FC and shows them in correct language
this is why this issue is bugging me… it should work on a view too because if term itself can distinguish between different languages of FC fields so can view via panel
I created view (page) in which I list all FC fields of all terms grouped by term name using relationship of that FC
content does change accordingly to the selected language =)
I created another view (content pane) as above and just added context filter, set it to termID and attach it to panels
view shows only FC fields of language that was used last when saving term. This mean that when editing and saving term in default language, view will only show fields of default language. weird :S
ET for FC enabled: it broke both views (showing fields of all languages everywhere), fixed by adding filter based on FC field: language and setting it to current user language
panels view still didn’t work as expected, but I knew that there was a problem with context filter
what I had to do is to remove validation criteria from context filter ( termID)
After solving last problem, view for panel is working and viewing term in both languages shows correct (translated) FC fields =).
Hope it helps understanding where problems occur and how to go around them. Fix would be nice though =)
Field Collections as a module has not yet been patched to support multilingual well. The debate is whether the field collection itself should be set to language-neutral, allowing the underlying fields to be language specific.
However, the field-collection module by itself does not currently support multilingual. There are a number of patches related to this on Drupal.org, including the following two major patch threads:
https://drupal.org/node/1344672
https://drupal.org/node/1316162
The Lingotek Translation module for Drupal 7 is successful at translating field collections and displaying them because it gets around the limitations of the Field Collection module using a combination of hook_entity_load, hook_entity_update, and a translation process that does not rely on the entity_translation module's UI.