cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
oml
Helper III
Helper III

Setting lookup field with JS not saved on submit

Hi,

 

I have a page that uses a basic form. 

 

On this basic form, I have 3 lookup fields;

oml_0-1702647342798.png


I'm currently using the out-of-the-box filtering when navigating from the top to the bottom of the lookup fields. This means that when I select a Property, the floor records are filtered to display only the floors related to the selected Property. The same goes for selecting a Floor, which filters the Property Units to only show those related to the selected Floor. This functionality works well.

 

However, in cases where the user directly selects a Property Unit without first selecting a Property and Floor, I retrieve the related Property and Floor from Dataverse using the Web API. This also works well, and I obtain the necessary data.

 

Now, the problem is that I need to set the Property and Floor lookup fields with the retrieved data. While I can successfully set the lookup fields with the data, the values are not saved when I submit the form. I'm not sure why this is happening. Is there something obvious that I'm missing here?

 

here is my full JavaScript code:

 

$(document).ready(function () {
    $("#flx_buildingunit").change(function () {
        console.log("hello from change event");
        // Get the selected value of the lookup field
        var selectedValue = $(this).val();
        
        console.log(selectedValue);

        // Show loading wheel while waiting for the response
        showLoading();

        fetchPropertyHierarchy(selectedValue);
    });
});

function fetchPropertyHierarchy(unitId) {
    webapi.safeAjax({
        type: "GET",
        url: "/_api/flx_buildingunits(" + unitId + ")?$expand=flx_BuildingFloor($select=flx_buildingfloorid,flx_floor),flx_BuildingTable($select=flx_buildingtableid,flx_buildingid)",
        contentType: "application/json",
        headers: {
            "Prefer": "odata.include-annotations=*"
        },
        success: function (data, textStatus, xhr) {
            debugger;
            // Hide the loading indicator when the response is received
            hideLoading();

            var result = data;
            console.log(result);
            // Columns
            var flx_buildingunitid = result["flx_buildingunitid"]; // Guid
            
            // Many To One Relationships
            if (result.hasOwnProperty("flx_BuildingFloor") && result["flx_BuildingFloor"] !== null) {
                var flx_BuildingFloor_flx_buildingfloorid = result["flx_BuildingFloor"]["flx_buildingfloorid"]; // Guid
                var flx_BuildingFloor_flx_floor = result["flx_BuildingFloor"]["flx_floor"]; // Text

                populateLookupField("flx_buildingfloor", flx_BuildingFloor_flx_buildingfloorid, flx_BuildingFloor_flx_floor, "flx_buildingfloor");
                hideLoading();
            }
            if (result.hasOwnProperty("flx_BuildingTable") && result["flx_BuildingTable"] !== null) {
                var flx_BuildingTable_flx_buildingtableid = result["flx_BuildingTable"]["flx_buildingtableid"]; // Guid
                var flx_BuildingTable_flx_buildingid = result["flx_BuildingTable"]["flx_buildingid"]; // Text

                populateLookupField("flx_buildingtable", flx_BuildingTable_flx_buildingtableid, flx_BuildingTable_flx_buildingid, "flx_buildingtable");
                hideLoading();
            }
        },
        error: function (xhr, textStatus, errorThrown) {
            // Hide the loading indicator in case of an error
            hideLoading();
            console.log(xhr);
        }
    });
}

function showLoading() {
    // Show the loading indicator
    $("#loadingIndicator").show();
}

function hideLoading() {
    // Hide the loading indicator
    $("#loadingIndicator").hide();
}

function populateLookupField(lookupFieldId, entityId, entityName, entityLogicalName) {
    // Set the ID part of the lookup field
    $("#" + lookupFieldId).attr("value", entityId);

    // Set the entity name part of the lookup field
    $("#" + lookupFieldId + "_name").attr("value", entityName);

    // Set the entity type part of the lookup field
    $("#" + lookupFieldId + "_entitytype").attr("value", entityLogicalName);
}

 

 

And this is my HTML code on the page:

 

{% include 'Portal Web API Wrapper' %}
<div class="row sectionBlockLayout text-left" style="display: flex; flex-wrap: wrap; margin: 0px; min-height: auto; padding: 8px;">
  <div class="container" style="display: flex; flex-wrap: wrap;">
    <!-- Loading indicator -->
    <div id="loadingIndicator" class="loading-container">
      <div class="loading-spinner"></div>
    </div>
    <div class="col-md-12 columnBlockLayout" style="flex-grow: 1; display: flex; flex-direction: column; min-width: 250px; word-break: break-word; padding: 16px; margin: 60px 0px;">{% entityform name: 'Ticket - Create' %}</div>
  </div>
</div>

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Hi @oml ,

 

To set a lookup value, you need to set following:

  • (column)Id
  • (column)_name
  • (column)_entityname

It seems your last attribute is not correct, please update your function populateLookupField to this:

 

function populateLookupField(lookupFieldId, entityId, entityName, entityLogicalName) {
    // Set the ID part of the lookup field
    $("#" + lookupFieldId).attr("value", entityId);

    // Set the name part of the lookup field
    $("#" + lookupFieldId + "_name").attr("value", entityName); //This would be the name of selected lookup value (That is displayed on form)

    // Set the entity name part of the lookup field
    $("#" + lookupFieldId + "_entityname").attr("value", entityLogicalName);
}

 

Please try and share if it works for you.

 

Thanks,

Saud

 

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

View solution in original post

1 REPLY 1

Hi @oml ,

 

To set a lookup value, you need to set following:

  • (column)Id
  • (column)_name
  • (column)_entityname

It seems your last attribute is not correct, please update your function populateLookupField to this:

 

function populateLookupField(lookupFieldId, entityId, entityName, entityLogicalName) {
    // Set the ID part of the lookup field
    $("#" + lookupFieldId).attr("value", entityId);

    // Set the name part of the lookup field
    $("#" + lookupFieldId + "_name").attr("value", entityName); //This would be the name of selected lookup value (That is displayed on form)

    // Set the entity name part of the lookup field
    $("#" + lookupFieldId + "_entityname").attr("value", entityLogicalName);
}

 

Please try and share if it works for you.

 

Thanks,

Saud

 

If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Results posted on July 24th

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 1: Community MembersSolutionsSuper UsersSolutionsPower Pages @Inogic  1   @ragavanrajan  2 @aofosu  1 @Jcook  1Open  @OliverRodrigues  1Open  @Lucas001  1Open Open    Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 2: Community MembersSolutionsSuper UsersSolutionsPower Pages @taraubianca25  2 @EmadBeshai  2 @ALP2  2@Fubar 2 @ekluth1  2@ragavanrajan 1 @mandela  1@OliverRodrigues 1 @Ajlan  1Open   @elishafxx  1    @TA_Jeremy  1    @helio1981  1       Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower PagesInogic2@EmadBeshai 6Ajlan1@ragavanrajan 4CraigWarnholtz1@Fubar 4  @Jcook 3  @OliverRodrigues2   Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower PagesHenryed071Fubar3Inogic1OliverRodrigues2JacoMathew1EmadBeshai2faruk11  TA_Jeremy1   shubhambhangale1   doug-ppc1   hubjes1  

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

  On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (3,763)