ManualSync and AS [Managed] Metadata

Hi All,
I am dealing with very large data sets and is thinking of
using "manualSync" (instead of
<auto-sync-enabled>true</auto-sync-enabled>) for
pushing server data updates to the clients. To use "manualSync",
the client code needs to subscribe to the DataServer for changes.
From reading the FDS user guide, it was not clear to me if FDS
would be able to handle data updates for me (after the client
subscribes to the changes).
Does having the [Managed] metadata tag in the AS class still
work when I am using "manualSync"? Or does the client now needs to
provide callback to handle updates from the manualSync channel?
Anyone has example on how to do this?
Thanks in advance!

Is your DIP customized?? as in with InfoPath?  From what I understand, InfoPath does not support managed metadata field types..  Just FYI...
There is a workaround for connecting to managed metadata shown here:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/632190d9-663b-4ea6-82e8-5c1e7f2f57c5/managed-metadata-columns-infopath?forum=sharepointadminprevious

Similar Messages

  • List view threshold and columns manage metadata problems

    Hi
    We have problem in our company since we have more files in library than is set in List view Threshold.
    I have created index on column "year" and create view filter: Year is equal 2015.
    and I get famous error: this view cannot be displayed because....
    I haven`t find any limitations on column type: manage metadata?

    Hi,
    As I understand, you encountered the issue after you created view filter.
    Every column type has the default number that can be created. You should go to check the number of your column created is less than the number by default.
    Per my test, I can achieve it without exceeding list view threshold.
    Check things below:
    1. You can increase the number of the list view threshold, and after that, you can try again to see the same situation will occur.
    2. Go to create another managed metadata column “year”, and create index on column "year", and create view filter in the same list to see the issue will occur.
    3. Check ULS log to see the details about the cause of the issue.
    Best regards,
    Sara Fan

  • In a document library : group by view and manage metadata filter & Navigation problem

    Hi all, I encounter a problem when configuring a document library using a group by view and in combination with the Managed Metadata filtering and
    navigation :
    - all the documents appear under my group by, even the ones that does not correspond
    - In the other hand, the number in brackets shows the correct number of documents that should be shown
    See screenshot below. 
    Did you already encounter that issue ? Is there a workaround ?

    Hi,
    According to your post, my understanding is that you wanted to use a group by view and combine with the Managed Metadata filtering and navigation in a document library
    to show the corresponding documents with the correct numbers in SharePoint 2013.
    In my SharePoint 2013, I created a view which was group by two columns and combine with the Metadata Navigation Hierarchies and Key Filters some fields in a document
    library. As a result, it showed only items matching the filter values.
    So, I recommend that you can follow the steps to implement it in your environment.
    Step1: Enable Metadata Navigation and Filtering:
    Metadata Navigation and Filtering is a Site Feature that has to be activated for this to work.
    And, the Metadata Navigation and Filtering feature is enabled by default on most sites.
    If it is not enabled for your site, you can enable it on the Site Features pages for your site.
    You must be a Site Owner or a Site Collection Administrator to enable Metadata Navigation and Filtering.
    1. Go to “Site Settings” and click “Manage site features” under Site Actions.
    2. Find “Metadata Navigation and Filtering” in the Features list and click “Activate”.
    Step2:
    Configure Metadata Navigation:
    You must have a least the Manage Lists permission level to configure metadata navigation for a list or library.
    1. Open the document library for which you want to configure metadata navigation.
    2. Go to “Library Settings” of the document library and click “Metadata navigation settings” under “General Settings”.
    3. In the Configure Navigation Hierarchies section, select the field or fields you want to display in the navigation hierarchy and then click “Add”.
    4. By default, Folders are automatically displayed in the navigation hierarchy. If you do not want folders to display, select Folders, and then click Remove.
    5. In the Configure Key Filters section, select the fields you want to add as Key Filters, and then click “Add”.
    6. In the Configure automatic column indexing for this list, specify whether you want to automatically create indices on this list to increase the performance of the
    queries that users will perform when they use the Navigation Hierarchy and Key Filter columns you've specified. It is recommended that you select the option “Automatically manage column indices on this list”.
    7. Click “OK”.
    Step3: Set a group by two columns by modifying view in the document library:
    1. Go to the “LIBRARY” ribbon of the document library and click the “Modify view”.
    2. Click the “Group By” and select up to two columns to determine what type of group and subgroup the items in the view will be displayed in.
    3. Click “OK”.
    Step4:
    Go back to the document library, apply Navigation Hierarchies and Key Filters to do a test in your environment.
    The result will like as below:
    There is an article about how to apply Metadata Navigation Filtering in SharePoint 2013 for your reference.
    http://blogs.interfacett.com/how-to-apply-metadata-navigation-filtering-in-sharepoint-2013
    Best Regards,
    Linda Li
    TechNet Community Support

  • Set Empty Managed Metadata Column - Working in 2010 and not in 2013

    I have seen posts similar to mine below but am still not finding a solution. I understand that setting an already populated managed metadata column can be problematic using SPD. However, my column is empty, and what works in 2010 is not working in 2013.
    Issue: In SharePoint 2010 On-premises, I am able to set an empty Managed Metadata column on a file in a document library via SPD workflow using the following format:
    ID;#Term|IdForTerm
    In SharePoint 2013 Online, I am attempting to create a SPD workflow to do the exact same thing (ID;#Term|IdForTerm) and am experiencing the following results depending upon the type of workflow I try:
    - SP 2010 Workflow - The workflow status result is Completed, but the managed metadata column remains empty.
    - SP 2013 Workflow - The workflow internal status becomes Started and effectively remains this way until I end the workflow.
    Any thoughts on what needs to change for 2013 when doing this? 
    Thanks in advance for any help or guidance.
    Alan

    Hi,
    I try to reproduce the issue in my SharePoint Online environment, however, everything works well.
    I create term set as below:
    Then start the workflow and the value in the browser view. The result is as below:
    I recommend to create another managed metadata column to check whether it works.
    Or you can create another library to check whether it works.
    Best Regards,
    Linda Li
    Linda Li
    TechNet Community Support

  • Managed Metadata Service and Content Type Hubs - Service Connection necessary?

    I created a site collection and activated the content type hub feature at the site collection level. We have an existing managed metadata service but I am unable to edit its settings, so I created a new MMS in a new database, however; there is no "service
    connection" row below the MMS row for the new MMS Application, but there is one for the old MMS Application. Will this still work with my content type hub? If not, how can I get the service connection setting/row? I have to do this via PowerShell since
    the menus in the ribbon are not usable due to our JavaScript settings...

    Are you using Custom claim provider??
    If you are then try this:
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/120ab535-63d2-4205-a51f-1987e9c0cf79/sharepoint-fba-the-content-type-texthtml-charsetutf8-of-the-response-message-does-not-match-the
    http://www.chapmanconsulting.ca/post/2010/04/23/The-Case-of-the-Failing-SharePoint-2010-FBA-Configuration.aspx
    #RoHsTr

  • Managed Metadata Refiner and Displaying the Full Path

    Does anyone know how best to work with the metadata refiner for a column that is set to show the full path of the tag?  We need to display the full path for this column when used in various views; however, when the full path is shown is the search refiner
    it is too long and run out into the search results.  (see picture)
    Is there a way to only show the tag name and not the full path to the tag within the refiner but still have it show the full path within libraries?  Thank you

    Daniel,
    Thank you for this article.  It looks like it would help, but when I replace the xslt with what's suggested in the article my refinement panel disappears.  Perhaps I'm not implementing it correctly.  I have a couple of managed metadata refiners
    listed as the first two refiners in the panel in addition to the usual ones such as author, date, site.
    What I did is that I replaced the xslt inside the <a> tags with the xlst mentioned in the article.
    <a class="ms-searchref-filterlink" href="{$SecureUrl}" title="{$RefineByHeading}: {$UrlTooltip}">
    <xsl:value-of select="Value"/></a>
    with
    <a class="ms-searchref-filterlink" href="{$SecureUrl}" title="{$RefineByHeading}: {$UrlTooltip}">
    <xsl:variable name="PartOfValue">
    <xsl:call-template name="substring-after-last">
    <xsl:with-param name="string" select="Value" />
    <xsl:with-param name="delimiter" select="':'" />
    </xsl:call-template>
    </xsl:variable>
    <xsl:variable name="PartOfTooltip">
    <xsl:call-template name="substring-after-last">
    <xsl:with-param name="string" select="$UrlTooltip" />
    <xsl:with-param name="delimiter" select="':'" />
    </xsl:call-template>
    </xsl:variable>
    <xsl:choose>
    <xsl:when test="($FilterCategoryType = 'Microsoft.Office.Server.Search.WebControls.TaxonomyFilterGenerator') and ($PartOfValue != '')">
    <xsl:if test="not(contains($PartOfValue, '…'))">
    <xsl:value-of select="$PartOfValue"/>
    </xsl:if>
    <xsl:if test="contains($PartOfValue, '…')">
    <xsl:value-of select="$PartOfTooltip"/>
    </xsl:if>
    </xsl:when>
    <xsl:otherwise>
    <xsl:value-of select="Value"/>
    </xsl:otherwise>
    </xsl:choose>
    </a>
    Is this correct? Thanks for the help.
    Matthew

  • Get Managed Metadata (Taxonomy) ALL Lists with Columns and ALL Choice Lists with Columns VALUES programmatically

    Hi there,
    How to get Managed Metadata Lists  ALL Columns and ALL Choice Lists Columns that are used in the Site Collection programmatically please.
    Regards

    Hi sharepointaju,
    Managed Metadata list is a hidden list, that you can access it through
    http://siteurl/Lists/TaxonomyHiddenList/AllItems.aspx, then it is similar to other lists, you can use server or client code to interate each field in the list, show the the value for each item.
    For all choice list columns, I'm not clear what you mean in this situation, do you mean to get all choice columns in the site collection, if so, iterate site columns, and lists to get list fields, check whether it is a choice type field.
    This may be not your requirement, please provide more information how you want to get which value.
    Thanks,
    Qiao Wei
    TechNet Community Support

  • User Profile Application and Managed Metadata services are missing

    Running SharePoint 2013 servers on a set of 2012 R2 Servers.  One of our farm administrators deleted the Secure Store service account.  They recreated the Secure Store account, but after doing so, the Managed Metadata Service and User Profile Service
    are now unavailable.
    When going to the User Profile Page, there is an error that says "Sorry, something went wrong."
    When going to the Metadata page, there is an error that says "The Managed Metadata Service or Connection is currently not available."
    There is an additional error that says "The Security Token Service is not available."
    How can all three services be brought back online?

    That specific event log error is as follows:
    WebHost failed to process a request.
    Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/12547953
    Exception: System.ServiceModel.ServiceActivationException: The service '/SecurityTokenServiceApplication/securitytoken.svc' cannot be activated due to an exception during compilation.  The exception message is: Exception has been thrown by the target
    of an invocation.. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentNullException: Value cannot be null.
    Parameter name: certificate
       at System.IdentityModel.Tokens.X509SecurityToken..ctor(X509Certificate2 certificate, String id, Boolean clone, Boolean disposable)
       at System.IdentityModel.Tokens.X509SecurityToken..ctor(X509Certificate2 certificate)
       at Microsoft.SharePoint.Administration.Claims.SPSecurityTokenServiceManager.ConfigureTokenHandlerCollection(SPSecurityTokenServiceManager manager, SecurityTokenHandlerCollectionManager collectionManager, String key, SecurityTokenHandlerCollection&
    tokenHandlerCollection)
       at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceConfiguration.ConfigureTokenHandlerCollectionForLocalIssuer(SPSecurityTokenServiceManager manager, SecurityTokenHandlerCollectionManager collectionManager, String key)
       at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceConfiguration..ctor()
       --- End of inner exception stack trace ---
       at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
       at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
       at System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(Type type, Boolean nonPublic)
       at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
       at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
       at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)
       at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceHostFactory.CreateSecurityTokenServiceConfiguration(String constructorString)
       at Microsoft.IdentityModel.Protocols.WSTrust.WSTrustServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
       at Microsoft.SharePoint.IdentityModel.SPSecurityTokenServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(ServiceActivationInfo serviceActivationInfo, EventTraceActivity eventTraceActivity)
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
       --- End of inner exception stack trace ---
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath, EventTraceActivity eventTraceActivity)
       at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath, EventTraceActivity eventTraceActivity)
    Process Name: w3wp
    Process ID: 5504

  • Managed Metadata (Failed to read from or write to database. Refresh and try again. If the problem persists, please contact the administrator)

    When creating a new site column of the managed meta data type in SharePoint2010, and you select "customize your term set", you are presented with one of the following errors:
    - This operation cannot be completed. The term store may be unavailable.
    - Failed to read from or write to database. Refresh and try again. If the problem persists, please contact the administrator

    Hi,
    I have been facing the same issue, however managed to resolve it.
    This is due to the uncommitted statements. From Powershell try running the following script
    #Connect to Central Admin, Replace the url with the environment specific URL
    $taxonomySite = get-SPSite http://centraladmin:40000
    #Connect to Term Store in the Managed Metadata Service Application, Ensure you put the right Metadate service application name
    $taxonomySession = Get-SPTaxonomySession -site $taxonomySite
    $termStore = $taxonomySession.TermStores["Managed Metadata Service"]
    write-host "Connection made with term store -"$termStore.Name
    #Connect to the Group and Term Set
    $termStore.RollbackAll()
    Hope it would help

  • Managed Metadata selection not appearing in Editform.aspx and DisplayForm.aspx after Managed Metadata column added to library.

    Hi,
    I added two managed metadata columns into a document library, but they are not appearing when you try to upload, or edit the properties of a document.
    In the Managed Metadata service the metadata is 'Available for Tagging' , and I've also looked at the permissions in
    http://sitenameLists/TaxonomyHiddenList/AllItems.aspx
    As one blog suggested, but this already has read access granted to NT AUTHORITY\Authenticated Users (NT AUTHORITY\authenticated users)
    The Connection Permissions in Central Admin, in the Managed Metadata Service Application has Full Access to Term Store granted for the service account that the application pool (Identity) is running under for the web app the site collection
    is in. 
    I've also deleted the whole document library and started over again, but the metadata selectors just don't show up for anyone, even when tried with the farm account.
    Any ideas what to investigate next appreciated.
    Thanks,
    Jonathan

    Ok, I think I've worked it out.
    It's to do with Content Types, if you add your own custom content type, then delete the default Document content type on a document library, before you add additional Managed Metadata columns to the library, they don't appear in the form. Another
    one for the Sharepoint quirks list.

  • When to use Managed Metadata service in Sharepoint 2013 and 2010

    Hi Folks,
    I have been working on sharepoint from quiet some time now. I have been using managed metadata service also.
    What I have not been able to find out so far is when should I be using MMS.
    What are the real advantages that I can draw out of it.
    I have one application that has Managed Metadata installed and has various terms stores and terms. 
    The Managed metadata service  created is utilized in search,
    What I do not know is what is why are we using it at all. 
    What is benefit of it.
    Managed metadata service could also be used in navigation is what i know.
    But what confused me is when is the best scenario to use it for navigation.
    Why can we not use the navigation provider in the managed metadata service. 
    There might be other uses also, but that is not clear to me.
    Can any one tell me why and in which scenario to really use it.
    I know how to configure the mms and how it works though the jargons around the managed metadata.
    Regards

    Managed Metadata has some specific advantages that make it useful for certain situations.
    A managed metadata column has the following advantages over a lookup or choice column:
    A managed metadata term set can be shared across the entire SharePoint farm, so you can use it in different site collections.
    You can set up "synonyms" so that multiple similar terms resolve to the same underlying piece of information
    Terms can be hierarchical (terms can be nested under other terms), and the SharePoint interface allows hierarchical filtering. For example, if I have a term set for Location, and one of my terms is North America, with terms below that for United States,
    Mexico, and Canada, I could choose to filter my list to show me all records with any North America location (inclusive of US, Mexico, and Canada), or to filter on a specific term (such as Mexico).
    You can allow people to enter new terms, which will then appear in the term set.
    You can specify information owners/stakeholders who maintain the term sets without them needing elevated access to sites; normally only site owners can mess with site columns and content types. Managed metadata lets you separate information management
    (what terms/synonyms should be used) from site management (granting access, creating groups and lists, etc).
    There are some disadvantages too. For example, with a lookup column, the lookup list can store additional columns of information. A managed metadata term set (on the other hand) only really stores terms (and descriptions/synonyms), but not related
    info. You might be tempted to do something like create a term set for part numbers, representing every part that your company produces; the term set would handle the part numbers just fine, but wouldn't let you add extra columns of information for
    description, weight, price, etc. In such a case, a lookup list is the better option.
    Microsoft has some suggested guidelines for when to use managed metadata/term store:
    SharePoint 2013:
    http://technet.microsoft.com/en-us/library/ee519604(v=office.15).aspx
    SharePoint 2010:
    http://technet.microsoft.com/en-us/library/ee519604(v=office.14).aspx
    A brief summary...
    Managed metadata is a good option when the potential metadata meets the following criteria:
    ​Is something for which a user will select a valid value​
    Represents information that is likely to be used multiple times
    ​Has valid values that can be organized hierarchically
    ​Includes synonyms or abbreviations that should be aggregated
    ​Can be applied in one language, but might be viewed in other languages
    Managed metadata is not a good option if the potential metadata meets any of the following criteria:
    Is represented by a built-in column (such as “last modified date”)
    ​Has an infinite number of valid values
    ​Has different valid values in each location that it is used (such as different values for the “version” attribute depending on which product team’s site the item appears in)*
    ​Has only “yes” and “no” as valid values
    *This type of metadata could still be captured in site collection-specific term stores

  • Sharepoint 2013 Public Facing Website With Managed Metadata Navigation on Office365 E3 Trial Online

    Warning: I am a complete novice in sharepoint
    I have subscribed to office365 online trial Enterprise edition to learn sharepoint
    I have created a Public facing Website
    Through the site-collection setting -> navigation created a new metadata group named navigation and chose it for global and current menu(I switched on the publishing service)
    Under the term Management I added two sub terms(for navigation group) with links to document and home.aspx
    The team site immediately showed the global menu with only two options(home and document) as needed
    Unfortunately the public facing site did not show any such options and instead showed a different menu(default one)
    I tried to add the navigation snippet to the master page and it showed the same default menu.
    The public site has no navigation option in Site setting either
    QUESTION: How can I get managed navigation in public facing site? Is it possible or it is not allowed?

    Hi,
    According to your post, my understanding is that you wanted to use the Managed Metadata Navigation in Public Website.
    Per my experience, we could not use the managed metadata navigation in public website, it is only available for the internal site collections.
    For more information:
    http://community.office365.com/en-us/forums/154/t/166500.aspx
    You can refer to the following article to know the public website and internal site collections on Office 365.
    http://blogs.sharepoint911.com/blogs/jennifer/Lists/Posts/Post.aspx?ID=76
    As this is the forum for the SharePoint server, , I’m not sure whether it supported managed metadata navigation now.
    I recommend you can post your question to the forum for SharePoint Online:
    http://community.office365.com/en-us/forums/154.aspx.
    More experts will assist you, then you will get more information relation to SharePoint Online.
    Thank you for your understanding and support.
    Thanks & Regards,
    Jason
    Jason Guo
    TechNet Community Support

  • How to show all the levels of managed metadata in Current navigation in SP 2013

    I am trying to use Managed metadata navigation as Current navigation/Left navigation Bar in a SharePoint intranet publishing site. I found one problem when I was configuring it:
    If we have the terms in the term set defined as follows:
    ├─> Root1
    │    ├─> L11
    │    │   ├─> L21
    │    │   │   └─> L31
    │    │   └─> L22
    │    ├─> L12
    │    └─> L13
    ├─> Root2
    └─> Root3
    (Please consider the indents as children of parent terms).
    So, there are 3 root terms and 4 levels of nesting in the terms. When I configured this for navigation it showed me only the 1st level by default i.e. Root1 -> L11, L12, L13 , Root2, Root3 in the navigation. So, the navigation is not fully displayed. If
    I navigate to a lower level, it shows me one more level below it and does not show the parent i.e. on navigating to L12, to shows me L21 and L22, but does not show the child L31 and the parent Root1. I presumed it would show me the full hierarchy.
    I did some probing around and figured that I could fix this by changing the master page. I navigated to the html file of the master page and within the vertical navigation snippet I found "PublishingNavigation:PortalSiteMapDataSource" that had these
    properties:
    StartFromCurrentNode(true) ShowStartingNode(false)
    I changed these values, that is, set 'StartFromCurrentNode' to false and 'ShowStartingNode' to true. I also set 'EnableViewState' to true which was false by default. Still , this did not fix the navigation
    Any help would be highly helpful and appreciated. Thanks

    Hi Sara,
    Thanks for the reply. I actually modified the setting what you mentioned but still I did not get the Top Level Navigation. I guess what you mentioned will work on the Top navigation. But I am trying to display the top 3 levels in the left navigation.
    ├─> Root1
    │    ├─> L11
    │    │   ├─> L21
    │    │   │   └─> L31
    │    │   └─> L22
    │    ├─> L12
    │    └─> L13
    ├─> Root2
    In the above tree, when i click on the L31 then the navigation is looking like 
                ├─> L21
                │   └─> L31
                └─> L22
    But I want to display like the below
        ├─> L11
        │   ├─> L21
        │   │   └─> L31
        │   └─> L22
    Regards... Mahesh

  • How to get the values of managed metadata columnn through object model

    Hi,
    I need to read the values from a managed metadata column, which is set to display entire path.
    Eg. My value looks like
    Critical:Important:Interesting:Routine:Not Evaluated
    without hardcoding these values, can i find which level of child has been chosen.
    if its not evaluated, i should find like last child like that..
    any way of doing that?
    Aruna

    Hi,
    thanks for the above reply.
    i got a new requirement as,  following is my managed metadata structure user selects the values from the below structure. i need to find the matching items with another list of same structure. the condition for matching is, if the user selects All,
    in the otehr list if the value in the region column equals any of the values in the structure below All like ema, denmark,nordborg is considered to be matched. if the user selects Denmark then the list contains denmark, nordborg and office is matched. means
    parent and its child contents are matched if the parent is chose. if the child is chosen only the exact value from other list(office==office in otehr list) is considered to be matched. how can i achieve it through object model coding?
    Aruna

  • How to Set Individual Managed Metadata Navigation Links to Open in New Window?

    I am using a managed metadata term set for the global navigation in my client's site. Most of the global navigation links point to pages in the current site, and should open in the current browser window/tab as the end user is just navigating within the
    site content. However, I have one particular node in the navigation term set that points to related content scattered around other external sites. The client wants these links to open a new window.
    Unfortunately, I can't seem to set the target for navigation links in the term set. If I was using standard global navigation, I'd be able to select the "Open in new window" checkbox when setting up the link, but that option doesn't appear to be
    supported via MMD navigation.
    Any clever suggestions?
    Thanks!

    I had a similarish requirement at a client once upon a time, they wanted any links that went outside of the intranet web applications to open in a new window.
    The way we managed that was to use jQuery to overwrite the standard hyperlink references for any hrefs that didn't point to internal sites to use the same javascript functions that SharePoint used for links configured to open in a new window. It worked out
    as being about half a dozen lines; check the URL and if it doesn't begin with a set range of options then overwrite the on click behaviour using standard jQuery behaviour.
    If you want it site wide then you just add jQuery and the code snippet to the master page, if you just want it in some places then add a CEWP or a HTML form web part to the relevant pages.

Maybe you are looking for