You are viewing limited content. For full access, please sign in.

Question

Question

Re-Order fields in Weblink Metadata pane

asked on March 13, 2020

Is there a way to re-order the fields that are in the metadata pane in Weblink? For some reason It's decided that multivalue field groups need to be first, and all of the rest of the fields are below them.

 

I promise that this isn't one that I've seriously messed with.

0 0

Replies

replied on March 13, 2020 Show version history

Hi Devin,

What version of WebLink is this? There was an known bug that matches this description in Weblink 10.0 that we fixed for 10.1. If you're 10.1 or higher, can you also provide screenshots of the following?

  • The same entry's metadata pane in Web Client
  • The template in the repo admin console showing field order

 

And we can look into it.

0 0
replied on March 16, 2020

The WebLink version is 10.2.0.264

Here is the metadata pane from Web Access 10.4 (10.4.2.214)

 

It may be of interest that I found the following in fields.xsl

<xsl:if test="count(Fields/Field[@InTemplate='true' and Value != '']) > 0 or count(Fields/FieldGroup) > 0">
              <div class="DataSection TemplateFields">
                <!-- Display each field group -->
                <xsl:for-each select="Fields/FieldGroup">
                  <div class="FieldGroup">
                    <xsl:for-each select="./FieldGroupRow">
                      <div class="FieldGroupRow">
                        <xsl:for-each select="./Field">
                          <div class="FieldDisplayName" title="{@FieldName}">
                            <xsl:value-of select="@FieldName"/>
                          </div>
                          <xsl:for-each select="Value">
                            <div class="FieldDisplayValue" title="{.}">
                              <xsl:choose>
                                <xsl:when test="/Fields/InsertLinks = 'True'">
                                  <xsl:call-template name="display_link_extract_url">
                                    <xsl:with-param name="val"><xsl:value-of select="."/></xsl:with-param>
                                  </xsl:call-template>
                                </xsl:when>
                                <xsl:otherwise>
                                  <xsl:value-of select="."/>
                                </xsl:otherwise>
                              </xsl:choose>
                            </div>
                          </xsl:for-each>
                        </xsl:for-each>
                      </div>
                    </xsl:for-each>
                  </div>
                </xsl:for-each>
                <!-- Display each field in template that is not in a field group  -->
                <xsl:for-each select="Fields/Field[@InTemplate='true']">
                  <!-- Remove blank field values -->
                  <xsl:if test="Value != ''">
                    <div class="FieldDisplayName">
                      <xsl:value-of select="@FieldName"/>
                    </div>
                    <xsl:for-each select="Value">
                      <div class="FieldDisplayValue">
                        <xsl:choose>
                          <xsl:when test="/Fields/InsertLinks = 'True'">
                            <xsl:call-template name="display_link_extract_url">
                              <xsl:with-param name="val"><xsl:value-of select="."/></xsl:with-param>
                            </xsl:call-template>
                          </xsl:when>
                          <xsl:otherwise>
                            <xsl:value-of select="."/>
                          </xsl:otherwise>
                        </xsl:choose>
                      </div>
                    </xsl:for-each>
                  </xsl:if>
                </xsl:for-each>
              </div>
            </xsl:if>

If this is used for what I think it's used for, it shows field groups being rendered before any other fields.

0 0
replied on January 21, 2021

Was there ever a resolution for this issue? We have LF WebLink Version 10.1.0.151 and the order of the metadata in WebLink does not match the order in Client (which is the order set up in the template).

0 0
replied on February 17, 2021

I haven't dug into it recently, but we never did get an answer. I might take another swing at it as part of a project I have coming up, and if I get anywhere I'll be sure to update this post.

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.