I am trying to create a Component1 in Tridion 2011 SP1. I also have Component2 which has already been created.
While creating a Component1 in Tridion, I have two fields for that Component, one is called 'SelectedType' which is a drop-down having values A,B,C which are options defined in the Schema. The other field called 'Name' which is also a drop-down, but its values should be retrieved from the second Component according to the value selected from 'SelectedType' field.
Component2 has the following fields named 'A', 'B','C'. Each field in Component2 is multivalued and is of type text.
So for example if I Select value 'A' from 'SelectedType' drop-down filed then my 'Name' drop-down field should get populated with the values fetched from field 'A' of Component2.
This functionality should not be implemented by adding any Extensions to the Tridion UI, or using any .NET code.
This should be purely implemented using the available functionality in Tridion.
Is there any scope of implementing event Handlers/Listeners in Tridion which populates values to the next drop-down field when an event has occured for the value change in first drop-down field?
This is not built-in functionality of Tridion, so you'll have to write some sort of extension. If you stick to the statement "without a GUI extension or .NET code" then the answer is a simple "no".
If you are willing to consider writing an extension AND you are on Tridion 2011 (or later), then you might be able to get this done using a Data Extender since the dependency you want is between two Components (and not fields within the same Component).
This will not be possible without creating a GUI extension I'm afraid. This functionality is not currently out of the box with SDL Tridion 2011. This is why the GUI is extendable.
Related
I have a CompositeField consisting of a LinkField and TextField in my dialog.
On select of data for LinkField, I want to populate the TextField also with a value related to the LinkField value.
Any idea how to do this?
This is for Magnolia CMS. I'm using the latest Magnolia version.
Thanks! :)
There is no ootb binding between different fields.
To create it, you would either need to write your own field that will internally encapsulate the link field and text field and register listener for link field value change and upon change set value for the text field.
Or you would need to rewrite dialog presenter to be able to register such listener on the link field when it's being created.
Sorry, don't have any code samples at the moment to demonstrate it. Hope the explanation is clear enough.
HTH,
Jan
Do you need to update the text field in view of the editor?
If not, this can be easily achieved by modifying the save action. Your form should have a commit button defined with class=info.magnolia.ui.admincentral.dialog.action.SaveDialogActionDefinition
Open SaveDialogActionDefinition and you'll see it points to info.magnolia.ui.admincentral.dialog.action.SaveDialogAction which, when executed, can manipulate the node before saving the session.
If you extended SaveDialogAction, added another method similar to setNodeName(Node node, JcrNodeAdapter item) and called it between setNodeName(...) and node.getSession().save(), you could set any additional property you wanted based on those entered by the user.
You would also need another definition class that referenced your new action so your dialog definition knew to use the new action on commit.
I am new to Adobe Livecycle and have created an XML dynamic form using Livecycle Designer ES4. I am looking for a way to promote a text field from the form to a custom property in the Forms Properties. An example would be the user fills in the field "TextField20" and after making that entry the custom property "Project Objective" in the forms properties is updated to reflect that information. Is it possible to promote metadata like this in Livecycle or is there another solution that I may not be thinking of? I tried researching online, but couldn't find anything related, which may be due to searching the wrong Adobe terminology/taxonomy.
I assume that you're talking about Variable tab in the form properties dialog.
In which case every property added creates a node in the form hierarchy with the name of the variables.
You only have to set this variable on the exit event of TextField20.
nameOfTheProperty.value = this.rawValue;
And that's it !
On Tridion 2011 SP1 HR1 publishing queue, I see user list is not sorted.
Is there a way to sort the user list or should I raise a ticket for a hot-fix?
Update:
To be more clear.
On Filter Publishing Task options --> User Dropdown, currently sorting is done based on User Title by default.
As a user, it's not appearing as sorted.
So, I'm looking for sorting the User Dropdown based on User Description.
Please suggest How can I achieve this.
Sort users in User dropdown on Publishing Queue popup could be achieved by creating new custom extension.
You add new js file to Publishing Queue popup group where you can overwrite Tridion.Cme.Views.PublishQueue.USER_DROPDOWN_HEAD_PATH property. It should point to Dropdown xml definition file. You'll need to create your own Dropdown xml definition file (by copying existing WebUI/Editors/CME/Xml/ListDefinitions/PublishQueueUserDropdown-head.xml) and add new node /list:listDefinition/list:rows/list:defaultSortField with value #Description.
On 2011 SP1 the user dropdown in the Filter Publishing Tasks options is sorted alphabetically by the username (User Title). And if you select "all", then in the Publishing Tasks list you can sort the task by username by clicking on the column heading. There is also a little funnel icon where you can filter further.
I am pretty sure this is by-design, so there will most likely not be a hotfix for this. You can submit an idea to have this feature implemented in one of the next releases via the Ideas site on sdltridionworld, or build a custom gui extension to do specifically what you need.
I have content type called news. I have a view thats lists all the news. But now I would like to filter those by year and type. User could select from select menu / dropdown the publish year (2010, 2011, 2012 so on) and also the type of the news (taxonymy terms).
I was playing around with views exposed but I only got a text input field. Can I somehow get a select menu instead of normal input field? And also how can I list all the publish years when news are published to that select menu?
Should this be done even with views?
====
PAGE
Filter dropdowns: -type- -year-
Press releaseses listed down here according the filters.
Select boxes will only be used in Views exposed filters when there is a finite number of possible values. In other words, if your field you want to filter on has something set in the 'allowed values' section you should have the option of a select box if you choose "FIELD NAME - Allowed Values" as the field to filter on in Views.
If your field has an unlimited amount of possible values, you could always write a custom module to create a block with a form that presents your select boxes and directs the user to the view (using the filter parameters of the view).
I'm using Profile to add a "Department" field to user profiles.
I'm using Views to create a view of users, with "Department" being an Exposed Filter.
The Exposed Filter is a textfield. I'd like for it to be a select dropdown that is populated with all possible values.
Is anyone aware of a module that will alter Views filters, changing fields from textfields to select dropdowns?
Drupal 6. Views 2. The profile field is a single-line textfield (with autocomplete).
i had the same issue in a project
fields that are textboxes show be select box.
as attachment image shows in 'FILTER CRITERIA' choose your field
in 'Filter type to expose' part choose 'Grouped filters'
a table will be shown that you manually can add your data as options
this solution is good when you know your options
this is my RTL settings for expose a textbox filter
this is my RTL settings for expose a textbox options
and in UI - client side this field will be shown like this
What kind of profile field is "Department"? I'm assuming it's one of single-line textfield, multi-line textfield, checkbox or list selection. I only tested it with a list selection, but if you check "Force single" then the exposed filter will be a select dropdown.
Assuming you mean Drupal 6. The above is true with Views 2.x and 3.x on D6.
If you want to modify an existing filter, follow the accepted solution provided here.
If altering an existing filter does not satisfy your requirements, then this step-by-step tutorial will help you creating your own custom Views filter.