Hello community,
I had problems to import string data into a picklist/optionlist.
In first run of dataflow it works fine on different entities.
Picklist is always the same.
In next run with some entities it works, in other there are strange error messages:
Either:
Error code: 0x8004431a, Message: A validation error occurred. The value 999999 of 'cr847_kcolor' on record of type 'cr847_dcars' is outside the valid range. Accepted Values: 742200000,742200001,742200002,742200003, ...
That's really funny, because imported colors are strings like red, blue and so on and sure not '999999'
Or:
"Data type mismatch with [ cr847_dcars.cr847_ktyp ] - Integer <-> String"
And again: Imported 'types' are strings like coupe, van and so on.
In first run there was no problem to convert a string into related option field.
I.e. 'red' imported as '742200000'
No, it didn't work to recreate this entity attribute again. So it is empty, at works like a first import. 😉
Any idea to solve?
Why it imports in two entoties and in two others, there are errors.
Thanks for help,
AndKan
Solved! Go to Solution.
Hello Eric,
your are right: error message makes sense, but DataFlows should be smart enough
It is smart ... and mysterious
1st error: "Error code: 0x8004431a, ... The value 999999... is outside the valid range. Accepted Values:..."
There was the value in picklist missing ...
Solution: Added the missing value into picklist and import works also.
2nd problem:
I recreated both entities new.
DataFlow import into pickuplist works fine.
Then I added an m:1 relationship and import fails again.
???
Related entity had no primary key; normally this is created with first import from SQL primary key.
Missing destination field cr847_entity02.cr847_id_entity01 in scheme
And pickup list has error Integer <-> String again.
So I removed relationship and: Import into picklist works again.
???
Solution:
- First I added a primary key manual.
- After that, I added m:1 relationship.
This workflow removes the error "Missing destination field ...".
And now the dataflow import works, including picklists.
And just another one:
I thought, my entity is crashed at all:
"General error","An item with the same key has already been added."
Of course there is a record with this key already, because Dataflow runs again. I'll try to update data.
This is a wrong error message ... It means: There is a duplicate entry in pickup list.
???
Solution:
Yeah ... you can enter any values like 'red', 'Red', 'reD' in pickuplist. No problem.
But you can only case-insensitiv import into picklist.
Otherwise you get the general error above.
Best regards,
AndKan
Hi @ganesh421,
Quick answer is that you can't. Choice (aka optionsets) are stored as integers in the database, so you'll have to find the integer representation of "Dog" and so on to import. You can simply do a find/replace in Excel.
To find the integer values, go to make.powerapps.com --> Data (sometimes called Dataverse) --> Tables --> select the table --> Columns --> select the column --> click on "Edit Choice" button --> click on the ellipses, view more.
Hope this helps!
Hi @AndKanPA,
Just trying to get a bit more context on your Dataflow. I assume your loading your data to an existing entity since option set destination type is not supported yet for new entities? Option set fields are represented by a key value pair where the key is an integer value and what's saved in the records. That said, the error message makes sense, but DataFlows should be smart enough to automatically map the data source label/text to the option set item display name. Would it be possible to share screenshots of the Edit Query and Mapping steps of the Dataflow?
Also, try to edit the flow, save and rerun to see if it works again or even create a new one?
Thanks
Hello Eric,
your are right: error message makes sense, but DataFlows should be smart enough
It is smart ... and mysterious
1st error: "Error code: 0x8004431a, ... The value 999999... is outside the valid range. Accepted Values:..."
There was the value in picklist missing ...
Solution: Added the missing value into picklist and import works also.
2nd problem:
I recreated both entities new.
DataFlow import into pickuplist works fine.
Then I added an m:1 relationship and import fails again.
???
Related entity had no primary key; normally this is created with first import from SQL primary key.
Missing destination field cr847_entity02.cr847_id_entity01 in scheme
And pickup list has error Integer <-> String again.
So I removed relationship and: Import into picklist works again.
???
Solution:
- First I added a primary key manual.
- After that, I added m:1 relationship.
This workflow removes the error "Missing destination field ...".
And now the dataflow import works, including picklists.
And just another one:
I thought, my entity is crashed at all:
"General error","An item with the same key has already been added."
Of course there is a record with this key already, because Dataflow runs again. I'll try to update data.
This is a wrong error message ... It means: There is a duplicate entry in pickup list.
???
Solution:
Yeah ... you can enter any values like 'red', 'Red', 'reD' in pickuplist. No problem.
But you can only case-insensitiv import into picklist.
Otherwise you get the general error above.
Best regards,
AndKan
Reason: Bad Request, Header x-ms-client-request-id d38da504-1eac-4dd7-aa94-dbe4a16d936a, Error code: 0x0, Message: An error occurred while validating input parameters: Microsoft.OData.ODataException: Cannot convert the literal 'Dog'' to the expected type 'Edm.Int32'. ---> System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.String.System.IConvertible.ToInt32(IFormatProvider provider) at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider) at Microsoft.OData.ODataPayloadValueConverter.ConvertStringValue(String stringValue, Type targetType) at Microsoft.OData.ODataPayloadValueConverter.ConvertFromPayloadValue(Object value, IEdmTypeReference edmTypeReference) --- End of inner exception stack trace --- at Microsoft.OData.ODataPayloadValueConverter.ConvertFromPayloadValue(Object value, IEdmTypeReference edmTypeReference) at Microsoft.Crm.Extensibility.ODataV4.CrmPrimitivePayloadValueConverter.ConvertFromPayloadValue(Object value, IEdmTypeReference edmTypeReference) at Microsoft.OData.JsonLight.ODataJsonLightReaderUtils.ConvertValue(Object value, IEdmPrimitiveTypeReference primitiveTypeReference, ODataMessageReaderSettings messageReaderSettings, Boolean validateNullValue, String propertyName, ODataPayloadValueConverter converter) at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadPrimitiveValue(Boolean insideJsonObjectValue, IEdmPrimitiveTypeReference expectedValueTypeReference, Boolean validateNullValue, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightPropertyAndValueDeserializer.ReadNonEntityValueImplementation(String payloadTypeName, IEdmTypeReference expectedTypeReference, PropertyAndAnnotationCollector propertyAndAnnotationCollector, CollectionWithoutExpectedTypeValidator collectionValidator, Boolean validateNullValue, Boolean isTopLevelPropertyValue, Boolean insideResourceValue, String propertyName, Nullable`1 isDynamicProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadEntryDataProperty(IODataJsonLightReaderResourceState resourceState, IEdmProperty edmProperty, String propertyTypeName) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadPropertyWithValue(IODataJsonLightReaderResourceState resourceState, String propertyName, Boolean isDeltaResourceSet) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.<>c__DisplayClass9_0.<ReadResourceContent>b__0(PropertyParsingResult propertyParsingResult, String propertyName) at Microsoft.OData.JsonLight.ODataJsonLightDeserializer.ProcessProperty(PropertyAndAnnotationCollector propertyAndAnnotationCollector, Func`2 readPropertyAnnotationValue, Action`2 handleProperty) at Microsoft.OData.JsonLight.ODataJsonLightResourceDeserializer.ReadResourceContent(IODataJsonLightReaderResourceState resourceState) at Microsoft.OData.JsonLight.ODataJsonLightReader.StartReadingResource() at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadResourceSetItemStart(PropertyAndAnnotationCollector propertyAndAnnotationCollector, SelectedPropertiesNode selectedProperties) at Microsoft.OData.JsonLight.ODataJsonLightReader.ReadAtStartImplementationSynchronously(PropertyAndAnnotationCollector propertyAndAnnotationCollector) at Microsoft.OData.ODataReaderCore.ReadImplementation() at Microsoft.OData.ODataReaderCore.InterceptException[T](Func`1 action) at System.Web.OData.Formatter.Deserialization.ODataReaderExtensions.ReadResourceOrResourceSet(ODataReader reader) at System.Web.OData.Formatter.Deserialization.ODataResourceDeserializer.Read(ODataMessageReader messageReader, Type type, ODataDeserializerContext readContext) at System.Web.OData.Formatter.ODataMediaTypeFormatter.ReadFromStream(Type type, Stream readStream, HttpContent content, IFormatterLogger formatterLogger)
I am getting this kind of error message When I am trying import data from excel. I tried to enter values for Species Column as 'Dog' in excel and upload, but still getting validation issue.
Reason: Bad Request, Header x-ms-client-request-id 81426f9e-c353-424f-b6b0-fbe7520c79dd, Error code: 0x8004431a, Message: A validation error occurred. The value 0 of 'cr8a6_species' on record of type 'cr8a6_pet' is outside the valid range. Accepted Values: 389490000,389490001
How can I enter String Values.
Thanks in Advance
Hi @ganesh421,
Quick answer is that you can't. Choice (aka optionsets) are stored as integers in the database, so you'll have to find the integer representation of "Dog" and so on to import. You can simply do a find/replace in Excel.
To find the integer values, go to make.powerapps.com --> Data (sometimes called Dataverse) --> Tables --> select the table --> Columns --> select the column --> click on "Edit Choice" button --> click on the ellipses, view more.
Hope this helps!
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!
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 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 Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8 SunilPashikanti8
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.
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