web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / The API operation 'Pos...
Power Automate
Answered

The API operation 'PostItem' requires the property 'item/emailaddress1' to be a string of maximum length '100' but is of length '101'

(0) ShareShare
ReportReport
Posted on by 132

Hello, 

I'm getting an error here sometimes and sometimes not:

//The 'inputs.parameters' of workflow operation 'Create_a_new_record_(deprecated)' of type 'OpenApiConnection' is not valid. Error details: The API operation 'PostItem' requires the property 'item/emailaddress1' to be a string of maximum length '100' but is of length '101'.//

 

zerou_0-1670527884782.png

 

Web capture_8-12-2022_133215_make.powerautomate.com.jpeg

Categories:
I have the same question (0)
  • Expiscornovus Profile Picture
    33,995 Most Valuable Professional on at

    Hi @zerou,

     

    It looks like you are using the Dynamics 365 connector with the Create a new record (deprecated) action, correct?

     

    If that is the case you are using a connector (Dynamics 365) which has been deprecated a while ago (05 May 2020):

    https://learn.microsoft.com/en-us/power-platform/important-changes-coming#dynamics-365-connector-is-deprecated

     

    Is there a reason why you are not using the Dataverse connector and the Add new row action instead?

  • Matthy79 Profile Picture
    4,188 Super User 2024 Season 1 on at

    Deprecated connector aside. If you try to store information and exceed the limit you will get a similar error when using a different connector. It looks like "emailaddress1" is set to a maximum of 100 characters and the email adress you are trying to save (sometimes) is larger than 100 characters. In this case 101. Try to add a compose action in front of the action that fails and print the email adress.

  • XeXE Profile Picture
    132 on at

    Hi guys I updated the flow but it's still failing. I'm not sure how to add the compose field in this case:

    zerou_0-1671594455202.png

    email field :

    zerou_1-1671594539620.png

     

  • Verified answer
    Matthy79 Profile Picture
    4,188 Super User 2024 Season 1 on at

    Hello @zerou 

     

    What is the error message? Is it still that the email adress is longer than the field length you want to store it in?

     

    To add the compose field you just need to put the same formular as in the email-field you want to store in the compose action (in front of the failing step). After the flow run you will see the value you want to store in the compose action output.

  • XeXE Profile Picture
    132 on at

    Yes, it's the same email string is too long message. I took a look at the outputs from a failed flow, and it seems to be capturing all the data sent into the form and treating it as an email, instead of just the email field.

     

    For what you're suggesting, are you saying I add a compose action in front of "add a new row" and out in the forumla that I'm using in the email field? 

     

    first(skip(split(first(split(body('Html_to_text'),'Phone')),'Email:'),1))
     
    Web capture_21-12-2022_1345_make.powerautomate.com.jpeg
  • Matthy79 Profile Picture
    4,188 Super User 2024 Season 1 on at

    Yes, that is what I meant but you already noticed that the value you are trying to store is not correct so you need to modify the formular to get the correct email. Maybe you try the same thing with the other fields too because it looks like you are using similar formulars for all the fields.

  • XeXE Profile Picture
    132 on at

    I was able to fix it by changing the formula for email to :

     

    first(split(last(split(outputs('Html_to_text')?['body'],'Email:')),'Topic'))

     

    Thanks !

  • XeXE Profile Picture
    132 on at

    *Sigh* So the problem has returned, the email step is still complaining about the string length. I added the compose function as well with the same formula as in the email expression, but it's returning the email *and* other text typed in, hence the string error.

     

    Update: Went back to the old formula: //first(skip(split(first(split(body('Html_to_text'),'Phone')),'Email:'),1))//

    And put that in the compose step instead, now it's working...for now. 

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 247 Super User 2026 Season 2

#2
11manish Profile Picture

11manish 164 Super User 2026 Season 2

#3
trice602 Profile Picture

trice602 138 Super User 2026 Season 2

Last 30 days Overall leaderboard