SQL Field - List View Data #15
Closed
opened 2016-07-17 17:59:00 +00:00 by paolavness
·
4 comments
No Branch/Tag Specified
No results found.
v5.1.0-rc2
v4.1.0-rc1
v3.2.5-rc1
v5.1.0-rc1
v4.0.4-beta3
v3.2.5-beta3
v5.0.4-beta3
v5.0.4-beta2
v4.0.4-beta2
v3.2.5-beta2
v5.0.4-beta1
v4.0.4-beta1
v3.2.5-beta1
v5.0.4-alpha3
v4.0.4-alpha3
v3.2.5-alpha3
v5.0.4-alpha2
v4.0.4-alpha2
v3.2.5-alpha2
v3.2.5-alpha1
v4.0.4-alpha1
v5.0.4-alpha1
v5.0.3
v4.0.3
v3.2.4
v5.0.3-beta3
v4.0.3-beta3
v3.2.4-beta3
v5.0.3-beta2
v4.0.3-beta2
v3.2.4-beta2
v5.0.3-beta1
v4.0.3-beta1
v3.2.4-beta1
v5.0.3-alpha4
v4.0.3-alpha4
v3.2.4-alpha4
v5.0.3-alpha3
v4.0.3-alpha3
v3.2.4-alpha3
v5.0.3-alpha2
v4.0.3-alpha2
v3.2.4-alpha2
v5.0.3-alpha1
v4.0.3-alpha1
v3.2.4-alpha1
v5.0.2
v4.0.2
v3.2.3
v3.2.3-beta4
v4.0.2-beta4
v5.0.2-beta4
v5.0.2-beta3
v4.0.2-beta3
v3.2.3-beta3
v3.2.3-beta2
v4.0.2-beta2
v5.0.2-beta2
v5.0.2-beta1
v4.0.2-beta1
v3.2.3-beta1
v5.0.2-alpha3
v4.0.2-alpha3
v3.2.3-alpha3
v5.0.2-alpha2
v4.0.2-alpha2
v3.2.3-alpha2
v5.0.2-alpha1
v4.0.2-alpha1
v3.2.3-alpha1
v5.0.1
v4.0.1
v3.2.2
v3.2.2-rc1
v4.0.1-rc1
v5.0.1-rc1
v5.0.1-beta5
v4.0.1-beta5
v3.2.2-beta5
v3.2.2-beta4
v4.0.1-beta4
v5.0.1-beta4
v3.2.2-beta3
v4.0.1-beta3
v5.0.1-beta3
v5.0.1-beta2
v4.0.1-beta2
v3.2.2-beta2
v3.2.2-beta1
v4.0.1-beta1
v5.0.1-beta1
v5.0.1-alpha7
v4.0.1-alpha7
v3.2.2-alpha7
v5.0.1-alpha6
v4.0.1-alpha6
v3.2.2-alpha6
v5.0.1-alpha5
v4.0.1-alpha5
v3.2.2-alpha5
v5.0.1-alpha4
v4.0.1-alpha4
v3.2.2-alpha4
v5.0.1-alpha3
v4.0.1-alpha3
v3.2.2-alpha3
v5.0.1-alpha2
v4.0.1-alpha2
v3.2.2-alpha2
v3.2.2-alpha1
v4.0.1-alpha1
v5.0.1-alpha1
v5.0.0
v4.0.0
v3.2.1
v3.2.0
v3.1.28
v3.1.27
v3.1.26
v3.1.24
v3.1.19
v3.1.17
v3.1.15
v3.1.12
v3.1.11
v3.1.10
v3.1.9
v3.1.8
v3.1.7
v3.1.6
v3.1.5
v3.1.4
v3.1.3
v3.1.2
v2.13.1
v2.13.0
v2.12.16
v2.12.15
v2.12.14
v2.12.10
v2.12.9
v2.12.8
v2.12.7
v2.12.6
v2.12.4
v2.12.3
v2.12.2
v2.11.7
v2.11.4
v2.11.3
v2.11.2
v2.11.0
v2.10.13
v2.10.11
v2.10.9
v2.10.5
v2.10.1
v2.10.0
v2.9.21
v2.9.18
v2.9.14
v2.9.11
v2.9.10
v2.9.8
v2.9.7
v2.9.1
v2.9.0
v2.8.5
v2.8.4
v2.8.2
v2.8.0
v2.7.10
v2.7.7
v2.7.6
v2.7.5
v2.7.4
v2.7.1
v2.7.0
v2.6.17
v2.6.16
v2.6.15
v2.6.14
v2.6.13
v2.6.12
v2.6.11
v2.6.10
v2.6.9
v2.6.8
v2.6.7
v2.6.6
v2.6.5
v2.6.3
v2.6.2
v2.6.1
v2.6.0
v2.5.8
v2.5.6
v2.5.5
v2.5.4
v2.5.1
v2.5.0
v2.4.10
v2.4.9
v2.4.8
v2.4.7
v2.4.6
v2.4.5
v2.4.4
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.10
v2.3.9
v2.3.8
v2.3.7
v2.3.6
v2.3.5
v2.3.4
v2.3.2
v2.3.1
v2.3.0
v2.2.10
v2.2.9
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.0
v2.1.21
v2.1.20
v2.1.19
v2.1.18
v2.1.17
v2.1.16
v2.1.14
v2.1.13
v2.1.12
v2.1.11
v2.1.10
v2.1.9
v2.1.8
v2.1.7
v2.1.6
v2.1.5
v2.1.4
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.9
v2.0.8
Milestone
No items
No Milestone
Paid Support
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: joomla/Component-Builder#15
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hey there, this is a question, not high priority right now.
With my countries custom SQL field - in list view of the all contacts, the id of the country is displayed, rather than the name of the country. Can you please point me in the right direction here, to get the country displaying in the list view.
Thanks!
Paola
Sure, take a closer look at the following tutorial, and let me know if you still have questions.
Hey there, aha... So this was helpful. I used a 'SQL' field for countries because the 'Custom' feel, in the section Field Information lists 'view' and 'views' as mandatory.
On exploring the dropbox custom fields, they are not. So I changed the type for from SQL to Custom, adding in the sql and removed the view & views attributes, and vwala, it works!
I'm wondering if any of the other attributes listed as 'mandatory' in the custom field type are not mandatory?
thanks again for quick response Llewellyn!
Paola
Well if it is marked as mandatory in the description, sure then it will use the default if you leave it out.
Remember even if you pull data from another component, it still has a single-view called view (check url) and a list-view called views (check url) . It will also have a table and a component name. Well that is if it is build like the core components.
You can still use the SQL field type, have a look at this also: https://docs.joomla.org/SQL_form_field_type
Yet I recommend using the Custom fields instead, it just seems more stable.
Check URL means in the back end it you open that view then the name that equals to
option=
is the view name.Also note that many of the details is used when you add this custom field to display in the list view and be sortable and part of filtering of this admin-view's (list view). If you do not add the field to the list view you can leave out many of the mandatory values and it will still work. So I marked all as mandatory so to insure everything is in place when needed for the various tasks.