sharepoint online taxonomy cascading dropdown - taxonomy

I have a custom filter webpart to which i want to add cascading drop down selection. I need the drop downs to populate using the parent and child nodes of the termset.
example term set hierarchy:
Country>>states>>cities
so my question is.. how can i use the termstore to populate 3 dropdowns and have them cascade based on the given hierarchy?

Try using SP services for the managed metadata field.
they have functions to get the hierarchy.

I know this is an old post, but maybe someone came across this and needs answers.
I found a Solution for this problem. It is called Branding.JSLink and you can find it on Github
I also found a blogpost where Github's solution has been adapted for multiple taxonomy fields.
Multivalue Taxonomy Field

Like Stefan said, answering an old post in case it helps someone.
Hope this newly contributed PnP sample addresses the requirement in the question for modern SharePoint.
For classic SharePoint, please refer this blog article.

Related

Two different Autodesk Forge apps are running same code

Please, it looks to me that I am asking a very basic question; however I could not find an explanation yet. I used .NET and both exercises for view models and modify models work great individually. I mean that I found no problems testing view models when this one was the only example available or modifying models when this one was the only example available. However, when both examples are available, doesn't matter which was the example selected and executed from inside Visual Studio that always goes to modifying models. Please notice that I created two different apps (obviously with different ClientId and secret key). Maybe not quite a good understanding of Autodesk Forge apps? Any help to understand what is going on?
Thank you very much!
If the two projects are in one solution you can specify which one to run as the default project as well as several projects at once and their order - see here and here...
Looks like this is rather a question on VS than Forge so I'd suggest to remove the autodesk-forge tag...

Is it possible to create variables on page1 and use that variable on page2? (Without the use of extensions)

I know it’s possible to create a template and have parameters, which can be used to customize another page. What I need to satisfy my colleagues, without the use of extensions, is to define variables in page1, such as end date, classification which i can use the variables on page 2. Similar as the use of template {{:page1|ParameterX|ParameterY}}.
My colleagues want to edit page1 (which consists all the details of a project)
Upon updating page1, they want page 2(which consists of an overview of many projects) to update with the information from the updated page1 data.
For example the project - end date has changed.
So the end date in page 2 of that specified project has changed too.
Thanks in advance.
As far as I know, this is not possible within traditional MediaWiki. One way to get the same effect would be to do as you suggested and work with templates. If multiple pages had the same information, you could use the common template, Template:2018 Project X - End Date as an example. Of course, with many variables, this could quickly become a messy approach. You could also create a template that has all the common information filled in and only requires input of differing information.
The alternative would be to simply have all the information verified by users across several pages.
A final potential option I am less familiar with, but which I believe may have a solution to your problem is using Semantic MediaWiki. It is a big extension, but a powerful one that may solve this and other problems down the line.

Canvas LMS REST API Quiz creation

I'm having an issue with quiz creation using the Canvas REST API:
I can create a new quiz with title set.
I can add N questions with the following parameters set:
question_name
question_text
question_type
points_possible
answers
When I look at my quizzes page, I can see the quiz exists, but it only shows that 1 question has been created for the quiz. I have to go to the quiz page, click the Edit button and then save the quiz for all of the questions to show up on the quizzes page.
What am I missing in this workflow?
So, for anyone interested in this question, the best solution I've been able to find is a hack. I tried doing comparisons of the quiz model data structure returned both before and after manually saving the quiz. There were some trivial differences, but only a couple meaningful ones. The only relevant difference was in the question_count attribute. It isn't being updated after adding questions.
To "fix" this: after adding your questions, manually update the question_count attribute (via a PUSH).
Perhaps this is a bug, perhaps I don't know what I'm doing. Either way, if anyone else has a better understanding of the Canvas REST API, please comment or provide a better answer.
Just ran into this same issue and here's a possible fix: Create the quiz first with published set to False. Add your questions. Then edit the quiz (https://canvas.instructure.com/doc/api/quizzes.html#method.quizzes/quizzes_api.update) to set published to True. Then add any overrides, etc.

How do I extend this Netbeans JSF2 CRUD example to have a single create and edit form for all entities?

I recently discovered this very useful Netbeans tutorial for creating a simple JSF 2 CRUD application http://netbeans.org/kb/docs/web/jsf20-crud.html. The final product has somewhat limited usability as one is confronted with a myriad of web pages. I would like an example of how to consolidate the Create and Edit forms (using the same project if possible). This seems more in keeping with how a person would actually enter such information and would reduce the risk of data entry mistakes. Why enter a client and their billing address on separate screens? One should be able to add or remove addresses, if need be, on the client's edit form. Or if a new client has multiple addresses, enter them all on the client's create form. The application just seemed incomplete with no further tips on how to improve it. If one has knows of a useful book that covers this, then I would gladly read that as well. Thanks.
I didn't realize the complexity of my problem and found that I couldn't get what I needed using JSF2 with the information resources available. Through my searches, I also found that many others were asking about Master-Detail CRUD applications, which I then learned was what I needed, but in slightly different ways and not getting any solid examples. A problem properly stated is half solved and I didn't know the problem statement. Armed with more knowledge, I was shocked to find that the answers were not readily available outside of some videos on YouTube showcasing Oracle ADF. In the end, I was able to quickly build the application I desired using the Play! Framework. In a way, by not having my question answered I was able to find a solution that would prove to be a better fit for my needs; though I would have gladly bought a cookbook if someone had pointed one out.

Terminology: What is this web gui action/type actually called

Terminology: What do you call this type of web gui feature?
I'm trying to research on a gui interaction where the user chooses an option, and the next set of options are loaded based on the previous.
I'm calling it cascading, but that doesn't seem to be right.
Example below:
User chooses company A
company A services load
user chooses service 1
serivce 1 loads, with only options company A wants
...cycle continues...
Silly question probably, but I am tired of getting all these search results that have nothing to do with what I'm after. Thanks in advance for any guidance.
If it matters, I'm thinking of using jquery for this, with C#/asp.net backend. Chose not to include those in the topic tags as I didn't think the language would change the terminology.
I think you're right with cascading if I understand you properly, ASP.Net/AJAX example here:
http://www.asp.net/ajax/ajaxcontroltoolkit/Samples/CascadingDropDown/CascadingDropDown.aspx