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

Invalid type. Expected String but got Null

Hi All,

 

Am very new to MS flow please help me one this.

 

Here I am triggered bot from MS flow when a new message enters on teams.

 

After that, I am running the bot with the UiPath orchestrator which working fine.

 

After sucessfull run the bot I want to reply to that message the task is done or NOT. So I’ve used parse JSON and below is my schema.

 

Sometimes it’s working fine some time I am getting errors inflow  "message": "Invalid type. Expected String but got Null.",

 

Can someone help me why sometimes it’s working fine and sometimes it’s not working fine, please advise how to resolve it.

 

Note: I’ve manually edit the JSON Parser allowing null type still this is not working some time.

 

"type": [

              "string",

              "null"

            ]

 

schema:

{

  "type": "object",

  "properties": {

    "value": {

      "type": "array",

      "items": {

        "type": "object",

        "properties": {

          "Key": {

            "type": "string"

          },

          "StartTime": {

            "type": "string"

          },

          "EndTime": {

            "type": "string"

          },

          "State": {

            "type": "string"

          },

          "JobPriority": {

            "type": "string"

          },

          "Source": {

            "type": "string"

          },

          "SourceType": {

            "type": "string"

          },

          "BatchExecutionKey": {

            "type": "string"

          },

          "Info": {

            "type": "string"

          },

          "CreationTime": {

            "type": "string"

          },

          "StartingScheduleId": {},

          "ReleaseName": {

            "type": "string"

          },

          "Type": {

            "type": "string"

          },

          "InputArguments": {

            "type": "string"

          },

          "OutputArguments": {

            "type": "string"

          },

          "HostMachineName": {

            "type": "string"

          },

          "HasMediaRecorded": {

            "type": "boolean"

          },

          "PersistenceId": {},

          "ResumeVersion": {},

          "StopStrategy": {},

          "RuntimeType": {

            "type": "string"

          },

          "RequiresUserInteraction": {

            "type": "boolean"

          },

          "ReleaseVersionId": {

            "type": "integer"

          },

          "EntryPointPath": {

            "type": "string"

          },

          "OrganizationUnitId": {

            "type": "integer"

          },

          "OrganizationUnitFullyQualifiedName": {

            "type": "string"

          },

          "Reference": {

            "type": "string"

          },

          "ProcessType": {

            "type": "string"

          },

          "ProfilingOptions": {},

          "Id": {

            "type": "integer"

          }

        },

        "required": [

          "Key",

          "StartTime",

          "EndTime",

          "State",

          "JobPriority",

          "Source",

          "SourceType",

          "BatchExecutionKey",

          "Info",

          "CreationTime",

          "StartingScheduleId",

          "ReleaseName",

          "Type",

          "InputArguments",

          "OutputArguments",

          "HostMachineName",

          "HasMediaRecorded",

          "PersistenceId",

          "ResumeVersion",

          "StopStrategy",

          "RuntimeType",

          "RequiresUserInteraction",

          "ReleaseVersionId",

          "EntryPointPath",

          "OrganizationUnitId",

          "OrganizationUnitFullyQualifiedName",

          "Reference",

          "ProcessType",

          "ProfilingOptions",

          "Id"

        ]

      }

    },

    "@odata.context": {

      "type": "string"

    },

    "@odata.count": {

      "type": "integer"

    }

  }

}

 

 

Thanks & Regards,

shagoul 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Modify schema about "EndTime" and "OutputArguments" properties.

-----------

"type": "string" ->  "type": [ "string",  "null"    ]

-----------

 

And delete them from "requiered" section.

 

The auto-generated schema is not perfect.

View solution in original post

Thank you, however, I find a solution by default I assigned some value in my argument now working fine. 

 

Every time when new value comes it will overwitire. 

View solution in original post

23 REPLIES 23

Which property is causing the error?

 

I’ve manually edit the JSON Parser allowing null type still this is not working some time.

 

This is the solution in many case.

If "required" section has an error property, try to delete.

 

 

 

 

Shagoul
Helper III
Helper III

 

This is flow I've edit the Schema in the JSON Parser

 

Shagoul_1-1625752022974.png

 

 

Can you check "Show raw outputs"?

It shoud say the name of the property that caused the error.

 

here it's 

Shagoul_0-1625752392836.png

 

Modify schema about "EndTime" and "OutputArguments" properties.

-----------

"type": "string" ->  "type": [ "string",  "null"    ]

-----------

 

And delete them from "requiered" section.

 

The auto-generated schema is not perfect.

You’re great 🙂 Thank you so much it’s working fine. however, will test again and let you know.

No problem! Waiting for your reply.

If my answer helps you, please click thumbs-up button.

 

Thanks.

Yes, it really helps, and any suggestion on how to format my output argument.

 

Now am getting out as curly brace like below.

 

The result" is the variable name I don’t want show “result” variable name and curly brackets { } .

 

How do I format my output with the right structure please advise.

Shagoul_0-1625753689831.png

 

 

 

Which action are you using? Share a screenshot with me.

Am just replying to the output via teams for that user.

 

Shagoul_0-1625755442027.png

 

Thanks.

There are many ways to do this, how about cutting the text you don't want to show?

 

replace('<text>', '<oldText>', '<newText>')

Reference guide for functions in expressions - Azure Logic Apps | Microsoft Docs

 

You can replace unwanted text with ''(nothing).

ex. replace ('{result: xxx}', '{result:', '')  -> 'xxx}'

 

You want to remove last bracket '}', so like this.

replace(replace('{result:xxx}', '{result:', ''), '}', '')

 

If you try, using 'Expression' tab.

MiyukiAmino_0-1625756618144.png

 

Shagoul
Helper III
Helper III

Thanks a ton 😊

You're welcome. Enjoy Power Automate!

Shagoul
Helper III
Helper III

Hi Again,

 

When I try to update the expression I am getting the expression is invalid. how can I format my output without curly brackets.

 

Example:  replace(replace('{result:xxx}', '{result:', ''), '}', '')

 

I’ve update my flow replace(replace('@{items('Apply_to_each_4')?['OutputArguments']}', '{result:', ''), '}', '')

 

 

Shagoul_0-1625817023331.png

 

Hi, thank you for reaching out.
 
You have to remove red charactor.
 
before:
replace(replace('@{items('Apply_to_each_4')?['OutputArguments']}', '{result:', ''), '}', '')
 
after:
replace(replace(items('Apply_to_each_4')['OutputArguments'], '{result:', ''), '}', '')
 
Try it.
Shagoul
Helper III
Helper III

Hi @MiyukiAmino ,

 

Shagoul_0-1627211169874.png

 

Still am facing the same issue any issue 

 

{
"type": "object",
"properties": {
"value": {
"type": "array",
"items": {
"type": "object",
"properties": {
"Key": {
"type": "string"
},
"StartTime": {},
"EndTime": {
"type": [
"string",
"null"
]
},
"State": {
"type": "string"
},
"JobPriority": {
"type": "string"
},
"Source": {
"type": "string"
},
"SourceType": {
"type": "string"
},
"BatchExecutionKey": {
"type": "string"
},
"Info": {},
"CreationTime": {
"type": "string"
},
"StartingScheduleId": {},
"ReleaseName": {
"type": "string"
},
"Type": {
"type": "string"
},
"InputArguments": {
"type": "string"
},
"OutputArguments": {
"type": [
"string",
"null"
]
},
"HostMachineName": {
"type": "string"
},
"HasMediaRecorded": {
"type": "boolean"
},
"PersistenceId": {},
"ResumeVersion": {},
"StopStrategy": {},
"RuntimeType": {},
"RequiresUserInteraction": {
"type": "boolean"
},
"ReleaseVersionId": {
"type": "integer"
},
"EntryPointPath": {
"type": "string"
},
"OrganizationUnitId": {
"type": "integer"
},
"OrganizationUnitFullyQualifiedName": {
"type": "string"
},
"Reference": {
"type": "string"
},
"ProcessType": {
"type": "string"
},
"ProfilingOptions": {},
"Id": {
"type": "integer"
}
},
"required": [
"Key",
"StartTime",
"State",
"JobPriority",
"Source",
"SourceType",
"BatchExecutionKey",
"Info",
"CreationTime",
"StartingScheduleId",
"ReleaseName",
"Type",
"InputArguments",
"HostMachineName",
"HasMediaRecorded",
"PersistenceId",
"ResumeVersion",
"StopStrategy",
"RuntimeType",
"RequiresUserInteraction",
"ReleaseVersionId",
"EntryPointPath",
"OrganizationUnitId",
"OrganizationUnitFullyQualifiedName",
"Reference",
"ProcessType",
"ProfilingOptions",
"Id"
]
}
},
"@odata.context": {
"type": "string"
},
"@odata.count": {
"type": "integer"
}
}
}

Yeah, "ReleaseVersionId" is still declared as "integer" only.

Rewrite schema like below and remove from "required section".

------------------

"ReleaseVersionId": {
"type":  [
"integer",
"null"
]
},

------------------

 

Hi Miyuki,

 

after replacing the above solution I got the below error message. 

 

Please advise what went wrong 

 

Shagoul_0-1627451333687.png

 

Hi, @Shagoul ! Thanks for reaching out!

 

Error message says 1st parameter ( '<text>' ) is null in "replace" function.

  replace('<text>', '<oldText>', '<newText>')

 

Please make sure that the parameters are set correctly in the function. Is there a case where it will be NULL?

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 | Winners will be 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.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (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. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     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 Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22   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 Automate Deenuji11FLMike31Sayan11ManishSolanki16VishnuReddy199710creativeopinion14Akshansh-Sharma3SudeepGhatakNZ7claudiovc2CFernandes5 misc2Nived_Nambiar5 Usernametwice232rzaneti5 eetuRobo2   Anil_g2   SharonS2  

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