nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom field value?

Nicole Holt

Hi everyone! I have a quick question--I see the end point for the category of a custom field, and the type of value the custom field may have (table entry, etc), but not the value of that table entry (aka the attribute description) . I'm willing to move the attribute from a table entry to the comment going forward, but I'm wondering if I am just missing something? Thanks for your help

Find more posts tagged with

Microsoft Power Platform

Comments

Ben Lambert

Hi Nicole,

Are you working in Power Automate? Or Power Apps?

Here's a related thread about custom field value (and some backstory for why you don't see a field for “value”):

The short version is, this is a known issues that we'd like to fix/improve. Would you be able to provide any more details on what you're ultimately trying to accomplish? We may be able to suggest a workaround (until we get a fix/improvement released).

Nicole Holt

Thanks for your reply Ben! I am working in Power Automate--I'm pulling a list of individuals who have signed up for a specific portion of our advocacy program. We've been coding the type of membership in that program through custom field that links back to a data table (So, the category would be “FAN Member” and the value on the drop down would be Individual, Group, Group Primary Contact"). I wish there was a better place to store this info, but it sort of got show-horned in when this new initiative was started.

The goal of the Power Automate flow is for the advocacy manager to have a ‘live’ cohort list with contact info & membership type (and I am sorry I keep using ‘membership’--we are not a membership organization, and this isn't tracked in the Membership mod).

Since this data was shoehorned in I don't have a lot of strong opinions about how it should be stored, so I am just as happy to move the table data over to the custom field comments. Which is what I've done for now--I was just wondering if there was something I was missing when reviewing my output options. I'll keep an eye out for for the fix.

Thanks again!