Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / PowerApps.. being able...
Microsoft Dynamics CRM (Archived)

PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

(1) ShareShare
ReportReport
Posted on by Iain_C_54 112

I have been exploring PowerApps a bit this week and I am hitting a bit of a road block with the what appears to be default display setting on a few fields.  I am wondering if anyone else has came across this and has been able to correct these?

I am guessing that as the PowerApp is connected directly to the database and not pulling the data from CRM it is returning the data as it is stored in the DB. It may be that the resolve is to update the 'Default' data field in the PowerApp to  call the 'logical' field but with out knowing the criteria to enter to call this I am a little stuck as to how this would be actioned. It may be that I just need to know the correct field to call..

8308.Default-data.jpg

The issues I appear to have at present are,

Where there is an option set, the power app shows the option set value number over the logical name. 

7750.Time-Entries-_0E202D00_-PowerApps_2D00_000242.jpg

In the app there appears no obvious way in which the range of options with in the option set can be displayed to then choose from.  As such presently the user would need to exactly the option they want and not only that they would need know the numerical value for that selection?

It also appears that when a users name should be displayed (owner and bookable resource), the PowerApp shows the GUID for that record and where hours and minutes are entered in CRM in the PowerApp this is then displayed as mins only?

8726.Time-Entries-_0E202D00_-PowerApps_2D00_000243.jpg

3531.Time-Entries-_0E202D00_-PowerApps_2D00_000245.jpg

*This post is locked for comments

  • Panoone Profile Picture
    Panoone 45 on at
    RE: PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

    Hi Iain,

    I'm having exactly the same issue and feel your pain and none of the replies here or on my post in the PowerUsers forum seem to have any bearing on our real world example.

    [View:https://powerusers.microsoft.com/t5/PowerApps-Forum/Dynamics-get-Customer-name-from-customerid-value/td-p/34420:750:50]

    There is NO Lookup control available in either the browser or desktop version of PowerApps for Dynamics entity datasources.

    It seems unfathomable to me that the default Case display form doesn't even allow me to include such basic info as the Case Number, Owner or Customer!

    case_2D00_viewform.png

  • Suggested answer
    ThomasN Profile Picture
    ThomasN 3,190 on at
    RE: PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

    Hi Lain,

    In the card there is a text input box. Delete just that text input box. Then insert from insert tab above the dropdown control. Drag to where that text insert box was. Then select the dropdown control, hold ctrl and select the text label and card objects, go up to action bar at top and find Group. This will give shared formatting and grouping of this content.

    On the dropbox control properties look at Default "Select an account" (for ex.) then Items type in the name of the table from a data source that you want to appear, for instance Accounts. Now this will show all the accounts in that table. Apply a filter to limit the items that are returned if necessary. Actually you may want to use the Lookup function as that allows for you to select what columns are returned, making it quicker as well. You need primary key and name, so in this example: Lookup(Accounts, state = "FL", accountid, name).

    Then set default to Accounts.name this will show the name.

    I am not sure but OnSelect can be set to Accounts.accounid, or the submit action can pull the Name of the Lookup.accountid to make sure and pass a GUID which is what CRM is expecting.

    powerapps.microsoft.com/.../function-filter-lookup

    Let me know if this points you in the right direction. Thanks.

  • Iain_C_54 Profile Picture
    Iain_C_54 112 on at
    RE: PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

    Hi Tom,

    I think I am missing something quite fundamental in this as I cannot see a way in which to change the text input fields to look ups? 
    or when on a blank form I cannot see how to insert a look up?

    Is that that it should be a look up function/formula?

    Iain

  • Iain_C_54 Profile Picture
    Iain_C_54 112 on at
    RE: PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

    Hi Tom

    Thanks for your reply.  No need to be sorry with the amount of info in your reply.  

    Its given me a lot to think over which is what I was looking for.

    The screen shots are taken from the power app which was built automatically and not from a blank app so I never really looked at the controls and data source as i assumed this would be matched by power app.

    From the limited time I have looked at power app I also feel that presently they are a little wanting.  Simple functions seem to be great but I am unsure if ultimately they are useful right now.  

    It seems to me that they are being presented in a way which suggests that almost no development knowledge is needed but I fear it's just not that simple.

    Again Thanks Tom for the info I need to go play some more.  

    Iain.

  • Verified answer
    ThomasN Profile Picture
    ThomasN 3,190 on at
    RE: PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

    Hi Lain, Thanks for reaching out.

    There is a lot going on here. I recently spent a few weeks digging into PowerApps and found them wanting. They do basic things great, and they make creating forms, and tools wonderful, but they have limitations that are key to making the platform useful.

    1. Edit Form
      1. This looks like you are using an OOB form created by powerapps.
      2. The form has cards on them and within each card are fields grouped together. A label, text input, etc.
      3. The data source of the form I assume is the CRM entity.
    2. Data Cards
      1. There is a data source for the card, which is pointing to the Parent.default. This means that card is going to the Form data source and getting the default value for that field.
      2. The value is formatted according to metadata in CRM. The last screenshot shows Default property = ThisItem.msdyn_type. the msdyn indicates it is pointing to the metadata.
      3. So for a field to show a specific value you call that field from the entity. ThisItem.name, or ThisItem.bookingresourcename the default is ThisItem.bookingresourceid, because lookups have both those values.
    3. Controls grouped in the card
      1. There are properties for the controls like text input that reference their parent which is a Card.
      2. When you create a display or edit form from the CRM data source through the power apps GUID this is all created correctly for you. Then take the form that is created and point the source to the grid list, or whatever the user is interacting with to select a specific record.
      3. A different scenario is if you have a custom edit or display form and then point the data source to another page which is a grid list where a user selects a record from a crm source.
        1. When doing this every card, and control needs to be validated.

    Sorry for all that butt wanted to provide some context. The issue is your data source and controls need to match. In the last screenshot, delete the text input control that is showing minutes. Insert a date control and point the source to Parent.default and you will get a date displayed. In the BookingResource control, change the text input field to a lookup, and research in PowerApps learning pages how to use a lookup with a data source. With a lookup, you can set the field to be displayed and the field to be submitted. That way it shows names, but submits GUID to the data source. Do the same for the Option Sets. Replace the Text input fields with Dropdown Input and set display name, and submit option number.

    Good Luck!

  • Iain_C_54 Profile Picture
    Iain_C_54 112 on at
    RE: PowerApps.. being able to display the logical data over the GUID's and show range of options in a option set

    Time-Entry_5F00_-New-Time-Entry-_2D00_-Internet-Explorer_2D00_000244.jpg

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Congratulations 2024 Spotlight Honorees

Kudos to all of our 2024 community stars! 🎉

Meet the Top 10 leaders for December

Congratulations to our December super stars! 🥳

Start Your Super User Journey

Join the ranks of our community heros! 🦹

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,711 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,458 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans