I have an Umbraco site for which I created an root node and child elements underneath it. The pages are there and I can find them in the 'Child items' tab, but I don't get the tree-like navigation in the admin content view. Is there some way to enable this?
Thanks!
It sounds like to have list view enabled on your document type. If you go back to the Settings section, navigate to the document type of your root node and click on the Structure tab you should see an 'Enable list view' option. Un-check this and the child items will appear in the tree.
You could also create your own tab called 'Child items' and then add a property of type 'List view'. This way you'll be able to have the content tree and list view active at the same time.
Related
If you have a TreeView in a VS Code extension, when you click on the items in it, they get selected (highlighted green, in my color theme). Click away from them and they get un-highlighted. See the below screenshot, in the file explorer view:
I'd like to "take control" of this behavior. I want to disable the highlighting that happens by default when the user clicks on these items, disable the un-highlighting that happens when they click away, and control in my extension code when the items get highlighted. I'd like to do this in my extension's custom TreeView, not an existing one.
Use the 'reveal' method of the treeview item. You can specify if it's to be 'selected' and also 'focused'.
Basically, you can change to the structure you want by forcing a refresh of the whole treeview. You probably already know that if you started making treeview extensions for vscode...
But then, right as it finishes re-rendering the tree, you 'reveal' a node, with the 'select' parameter option, to have that node as the selection in the tree. ...To have another node selected, just 'reveal' another one. (no need to force a full refresh of the treeview if it's only to have another node selected without changing the structure of the tree.)
see the 'reveal' method of the treeview here treeview API
Also see the leointeg extension on vscode for actual code example of controlling which node is selected
Click on the new button in the project template lookup field of the project entity,this opens a quick create form which will have all the fields
Also click on the new button from the top upper right corner of nav bar and select project entity. This also opens a quick create form with all the fields.
Now I want to distinguish from where the quick create form is opened(from the lookup new button or from the nav bar).
I would like to have a solution for this in UCI not in web client
Literally No way.
The same Quick create form is opened in exact same way from both Lookup (New +) and Top Navigation bar Quick create button (+).
https://abc.crm.dynamics.com/api/data/v9.0/GetClientMetadata(ClientMetadataQuery=#ClientMetadataQuery)?#ClientMetadataQuery={%22MetadataType%22:%22form%22,%22MetadataSubtype%22:%22QuickCreate%22,%22EntityLogicalName%22:%22contact%22,%22MetadataId%22:null,%22MetadataNames%22:[],%22GetDefault%22:true,%22DependencyDepth%22:%22OnDemandWithContext%22,%22ChangedAfter%22:%22777574980%22,%22Exclude%22:[],%22AppId%22:%22edcd61cf-1f0c-e811-a95f-000d3a18032d%22}
Probably can think about workaround, when we understand what you are trying to achieve.
Atleast Quick create form opened from Subgrid will have pre-populated parent lookup to identify the source. This is like dead end.
On the order form, there is a products section that has uses the default Order Product Inline Edit View. This view is not editable, but you can copy it and save it as a different name.
However, when you copy the view, the new view does not display all of the same buttons when viewing the sub-grid.
default view:
copied view (the lock pricing, move up and move down buttons are missing):
The copied view shows the + button and it's drop down menu correctly. Why hasn't it copied the other buttons, and how can i get them to show on my custom view?
I am happy to edit xml and upload that back to CRM if necessary.
Update:
FYI, this is all a pointless effort as the word template ignores the sequence order. What an utter waste of time.
I'm going to guess it's because the default view on the order of order products is a special one. It has special behaviours that arn't seen in the rest of 365, i.e. you don't get up, down, or lock on other views.
I would assume that the extra buttons only get shown on that default view and arn't really supported outside of that view.
Turns out it is actually quite easy to show these buttons for other views using the ribbon workbench.
Right click on the button in ribbon workbench under the subgrid section and click on customise
Select the command in the "solution elements" pane at the bottom
In the bottom right hand pane, right click on the enable rule "Mscrm.IsInlineEditView" and click "Remove from Command"
Publish
These buttons now show up for all views.
I have a certain View.
In this view there is a TreeViewer.
When I right-click one element of the tree, I open the contextual menu that trigger the command "rename".
In the HANDLER of this command, how can I obtain the ID of the view of the selected element?
Is it possible to get it?
Thanks very much to everyone will answer!
See HandlerUtil. In this example, since you right-click on an element in a view, it should become active and you can use
HandlerUtil.getActivePartId(e);
I have a Prism/SL3 application with a tab control and each page of the tab control is a "Region" that has its own view and viewModel. when I want to validate the main page, I call dataForm.ValidateItem(), then I go to all the child views and do the same. the problem is, only the pages which user has clicked on them (on the tab page), get instantiated and the pages that are never shown, don't have their view instantiated, thus I can't validate them.
any help?
I created a psuedo work around for this. It's very hacky, but it does work. My example involved walking the visual tree (up and down) to find respective controls that are invalid and then "expanding" the selected item. I have used an accordian in my example, but have also tested this with tab:
http://thoughtjelly.wordpress.com/2009/09/24/walking-the-xaml-visualtree-to-find-a-parent-of-type-t/
HTH,
Mark
EDIT: Link updated.