cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

The property expects Table values, but this rule produces incompatible Boolean values

Below are links to two screen prints. They are for a PowerApp using the new barcode scanner. The purpose of the app is to scan a book's ISBN, then get information from a database and return information about the book. The Swagger file results in a successful response (see image at link).

 

Issue 1: I have two instances of the app saved. One is shared and the other is not. When I try to load the unshared instance for editing, the "Downloading" overlay appears and never completes loading the app in edit mode. The shared instance loads for editing. Is there a way to "unshare" to permit additional edits? Or is something else causing the problem?

 

Issue 2: If the Items property of Gallery1 is set to 'BookByISBN2.txt'.GetISBNSearch(Scanned_ISBN), the result is "The property expects Table values, but this rule produces incompatible Boolean values". If I replace "Scanned_ISBN" with an actual ISBN, the same message appears. How can this Items statement be corrected? The intent is to scan an ISBN, search the database for that ISBN, then return it to Gallery1.

 

Issue 3: When scanning the barcode in PowerApps online, the image is rotated 90 degrees and scanning does not work (at least not well).  When using PowerApps Studio, the barcode scanning image does NOT rotate (it is oriented properly and scanning works). This issue has been reported previously in the " scanning" Ideas section of the PowerApps Community. I assume this has been identified for a fix by the PA Team.

 

Any help will be very much appreciated!

Swagger File Is Valid

Gallery1 Items Statement

2 ACCEPTED SOLUTIONS

Accepted Solutions

 

The order of properties does not make a difference. Only their names and types matter.

Unfortunately I cannot paste formatted content here, but can you please try the following 200 response (below):

 

(this is assuming that author_data and subject_ids are both arrays of objects, but it does not declare the schema of those objects, since the schema is not obvious from the sample response you included). 

 

"200": {

"description": "Successful Operation",
"schema": {
"type": "object",
"properties": {
"index_searched": {
"type": "string"
},
"data": {
"type": "array",
"items": {
"type": "object",
"properties": {
"title_long": {
"type": "string"
},
"author_data": {
"type": "array",
"items": {
"type": "object"
}
},
"summary": {
"type": "string"
},
"physical_description_text": {
"type": "string"
},
"publisher_text": {
"type": "string"
},
"urls_text": {
"type": "string"
},
"publisher_name": {
"type": "string"
},
"publisher_id": {
"type": "string"
},
"language": {
"type": "string"
},
"title_latin": {
"type": "string"
},
"edition_info": {
"type": "string"
},
"dewey_decimal": {
"type": "string"
},
"isbn10": {
"type": "string"
},
"title": {
"type": "string"
},
"lcc_number": {
"type": "string"
},
"dewey_normal": {
"type": "string"
},
"marc_enc_level": {
"type": "string"
},
"notes": {
"type": "string"
},
"book_id": {
"type": "string"
},
"awards_text": {
"type": "string"
},
"isbn13": {
"type": "string"
},
"subject_ids": {
"type": "array",
"items": {
"type": "object"
}
}
}
}
}
}
}
},

Radu Gruian [MSFT] ** PowerApps Staff

View solution in original post

Unfortunately, Swagger 2.0 does not allow query strings in paths.

See the following on reasons why this is the case: Proposal: Querystring in Path Specification

 

You can see this by the fact that the '?' char in your path is being escaped (per url escaping protocol). Also, there is likely a weird thing going on with connectors which is possibly masking the actual problem. But this is definately the cause of the problem. In all likelyhood, the connector is passing to your service a url which is further messed up.

 

You should fix your paths to be Swagger compliant.

I have filed a task on our plate to detect this scenario and to reject any Swaggers that contain the '?' char in the path string.

 

One thing that you'll hit though is that you'll have to actually specify the parameters with no values. This is unfortunate as you'll have to specify the parameters in the rules. But first thing is to be explicit. I'd recommend specifying the parameter as type:"string" for now and just specifying "json" in the function call to unblock you.

View solution in original post

25 REPLIES 25
rgruian
Power Apps
Power Apps

Hi ExCessna,

 

In PowerApps, galleries are used to visualize aspects of tabular data (tables). Please see this link for more information on how to use galleries in PowerApps:

https://powerapps.microsoft.com/en-us/tutorials/add-gallery/

 

In your case, the GetISBNSearch api returns a single boolean value. You cannot bind a gallery to a scalar boolean value, since that would provide no useful data for the gallery to render (it needs rows of data instead, with each row containing one or more fields).

 

What is the signature of your GetISBNSearch function, and/or the swagger declaration? What is the function really supposed to return? (i.e. what is a successful ISBN retrieval expected to look like, data-wise).

 

Radu Gruian [MSFT] ** PowerApps Staff

Radu,

Thank you for your reply. I think I understand what you are saying about the message. The Swagger Definition, as seen in the Swagger editor, is below (I hope this is the declaration you asked about). I thought the Swagger was returning a row of information (see "Swagger File Is Valid" link). The information under "Data" is what I want to have returned. I am new to Swagger and am studying it in more depth, but I'm hoping you can suggest something I can do to capture this information.

Thanks very much for your help!

000-Original Swagger Def.png

 

 

Can you please copy-paste the swagger content (json) here, or at least the entire part relevant to Get_ISBNSearch_ ?

I need to see how it declares the result data type.

 

Here are the customizations you need to make to correctly pull your custom API into PowerApps:

https://powerapps.microsoft.com/en-us/tutorials/customapi-how-to-swagger/

 

The Swagger spec can be found here:
https://github.com/OAI/OpenAPI-Specification/blob/master/versions/1.2.md


Also see the Hello World example:
https://github.com/OAI/OpenAPI-Specification/wiki/Hello-World-Sample

 

Radu Gruian [MSFT] ** PowerApps Staff

Radu,

Here is the JSON output from the Swagger editor. I hope it is what you need. It was what I used to upload into the Custom API connector:

{
"swagger": "2.0",
"info": {
"version": "1.0",
"title": "BookByISBN2.txt",
"description": "ISBNdb retrieval of book information by ISBN",
"license": {
"name": "MIT",
"url": "http://github.com/gruntjs/grunt/blob/master/LICENSE-MIT"
}
},
"host": "isbndb.com",
"basePath": "/",
"securityDefinitions": {},
"consumes": [
"application/json"
],
"produces": [
"application/json"
],
"paths": {
"/api/v2/json/My API Key/book/{book}": {
"get": {
"description": "Get Book Information by ISBN",
"operationId": "Get_ISBNSearch_",
"produces": [
"application/json"
],
"parameters": [
{
"name": "book",
"in": "path",
"required": true,
"x-is-map": false,
"type": "string",
"description": "Book ISBN"
}
],
"responses": {
"200": {
"description": "Successful Operation"
},
"400": {
"description": "Bad Request"
},
"404": {
"description": "Not Found"
},
"500": {
"description": "Internal server error"
}
}
}
}
}
}

 

I used an online converter to take a WADL file which had been generated for a Project Sienna app and convert it to Swagger. The original file would not generate, as it did not like "Query" in the WADL. (see Swagger Definition File Creation). The entire row of data was specifically defined in the WADL, but was lost in the conversion. However, I thought somehow I was still getting the row of data because I see it in the response.

 

Thanks again!

I don't know whether this will help, but here is the WADL file that retrieved the data needed in Project Sienna. I see there is more to this file than appears in the Swagger.

 

xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:sienatool="http://www.todo.com" siena:serviceId="BookByISBN" xmlns="http://wadl.dev.java.net/2009/02">
<grammars>
<siena:jsonTypes targetNamespace="http://www.todo.com" xmlns:wadl="http://wadl.dev.java.net/2009/02">
<siena:object name="ISBNSearch_Root">
<siena:property name="index_searched" type="string" />
<siena:property name="data" typeRef="ISBNSearch_data_Array" />
</siena:object>
<siena:object name="ISBNSearch_data_Object">
<siena:property name="title_long" type="string" />
<siena:property name="dewey_normal" type="string" />
<siena:property name="edition_info" type="string" />
<siena:property name="awards_text" type="string" />
<siena:property name="urls_text" type="string" />
<siena:property name="subject_ids" typeRef="StringArray" />
<siena:property name="title" type="string" />
<siena:property name="marc_enc_level" type="string" />
<siena:property name="author_data" typeRef="ISBNSearch_author_data_Array" />
<siena:property name="physical_description_text" type="string" />
<siena:property name="summary" type="string" />
<siena:property name="lcc_number" type="string" />
<siena:property name="book_id" type="string" />
<siena:property name="title_latin" type="string" />
<siena:property name="publisher_id" type="string" />
<siena:property name="publisher_text" type="string" />
<siena:property name="language" type="string" />
<siena:property name="isbn10" type="string" />
<siena:property name="publisher_name" type="string" />
<siena:property name="dewey_decimal" type="string" />
<siena:property name="isbn13" type="string" />
<siena:property name="notes" type="string" />
</siena:object>
<siena:array name="StringArray" type="string" />
<siena:object name="ISBNSearch_author_data_Object">
<siena:property name="name" type="string" />
<siena:property name="id" type="string" />
</siena:object>
<siena:array name="ISBNSearch_author_data_Array" typeRef="ISBNSearch_author_data_Object" />
<siena:array name="ISBNSearch_data_Array" typeRef="ISBNSearch_data_Object" />
</siena:jsonTypes>
</grammars>
<siena:authenticationProviders />
<siena:template>
<siena:variable name="ApplicationKey" isSecret="true">
<siena:doc title="Application Key" />
<siena:modifyParams name="/book" attribute="fixed" format="{0}" />
</siena:variable>
</siena:template>
<resources base="http://isbndb.com">
<resource path="api/v2/json/My_API_Key/book/9780849303159">
<method name="Get" id="ISBNSearch" siena:requiresAuthentication="false">
<request>
<param name="/book" required="true" style="Query" />
</request>
<response siena:resultForm="single">
<representation mediaType="application/json">
<param name="ISBNSearch_Name" type="sienatool:ISBNSearch_Root" style="Plain" path="" />
</representation>
</response>
</method>
</resource>
</resources>
</application> 

Hi ExCessna,

 

 

It looks like your swagger is not declaring the result type for the function.

 

"200": {
    "description": "Successful Operation"
},

 

You may want to augment the declaration with a return type, so that PowerApps understands what will be expected from this API. The resulting schema will then be available in Intellisense, and will make the type-related errors you previously saw (bool vs table) go away.

 

See the Swagger 2.0 spec on the Responses object:

https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#responsesObject

 

I believe you need to add a "schema" object in the "200" response:

 

"200": {
    "description": "Successful Operation"
    "schema": {

        "type": "array",
         "items": { ..... the row type here .... } 

    }

}

 

Can you give that a shot?

 

 

 

 

Radu Gruian [MSFT] ** PowerApps Staff

Radu,

 

I"m working on it and think I'm beginning to see the light. I'll mark your reply as the answer once I figure it out. Thanks very much for your help!

I was prompted to reply, so here's the status of my attempts at the Swagger. Is this close? How do I correct the error?

 

1. The modified Swagger is below:

First half of Swagger responseFirst half of Swagger responseSecond half of Swagger responseSecond half of Swagger response

When the above is run in the Swagger editor, it indicates the response is a success and returns the data I'm trying to get:

First half of Swagger editor response success, renderedFirst half of Swagger editor response success, renderedSecond half of Swagger editor response success, renderedSecond half of Swagger editor response success, rendered

But when the connection is added in PowerApps, it results in this message:

PowerApps error messagePowerApps error message

If I ignore this message and click "Create", then try to add it into the PowerApp, the following error message is displayed:

No wadlUrlNo wadlUrl

I was prompted to reply, so here's the status of my attempts at the Swagger. Is this close? How do I correct the error (see below)?

 

1. The modified Swagger is below:

First half of Swagger responseFirst half of Swagger responseSecond half of Swagger responseSecond half of Swagger response

When the above is run in the Swagger editor, it indicates the response is a success and returns the data I'm trying to get:

First half of Swagger editor response success, renderedFirst half of Swagger editor response success, renderedSecond half of Swagger editor response success, renderedSecond half of Swagger editor response success, rendered

But when the connection is added in PowerApps, it results in this message:

PowerApps error messagePowerApps error message

If I ignore this message and click "Create", then try to add it into the PowerApp, the following error message is displayed:

No wadlUrlNo wadlUrl

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!

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.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

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 in the Forums 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. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     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. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     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 Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27  

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

Top Solution Authors
Top Kudoed Authors
Users online (3,020)