Unexpected behavior in Smart Import (Value in cell xx must be one of the suggested values)

Krisztina Zappert · 2023-04-17T14:07:26+00:00

There was an error rendering this rich post.

Hi,

I have encountered some unexpected behavior in Smart Import that I hope the community has an answer for.

I am building a Smart Import screen, and it involves 4 month columns. One of the columns is mapped to the entity Month, 3 to text cubes. All 4 columns have "suggested values defined", all of them look at Month code, and all of them have the "Based on Cube" checked, so they don't show all months.

As I go to test the input, however, I get an error message saying the entered values are wrong.

I cannot make these errors go away. I am choosing from the list, I am not doing any data entry. I have tried turning "Based on Cube" off, just to see that it works, and the result is the same. (All 3 column drop downs are based on the same cube)

Interestingly, the 4th month column (mapped to entity, and it only has 1 "correct" month, the currently open month, so it uses another cube for validation), works fine.

Has anyone encountered similar issues? Any tips on how I can solve this?

Find more posts tagged with

Accepted answers

Krisztina Zappert

Hi again Neha,

Upon further testing, I found the issue. I had a selector on the month 202211, and for some reason, even though other months appeared in the drop down list, only this month was accepted.

As soon as I removed the month selection in the screen, all the other months were accepted by the tool as valid inputs.

The cubes remained text types, and the drop down list consisted of month codes.

Thank you,

Krisztina

All comments

Krisztina Zappert

Further notes: It works when I put in the first available month.

This is what all the drop downs look like. When I select 202211, input goes through. When I select any other month, I get the error message. This happens in all 3 cases.

Any ideas?

Neha Hasija

Hi Krisztina,

As column b,c,d are date type you need to input the date and not month.

For Example : 01/01/2023

Also, month column should be based on suggested values.

This should resolve the error messages

I would recommend to first try month, date, date, date without any suggested values and then try implementing the suggested values.

Regards,

Neha Hasija

Krisztina Zappert

Hi Neha, Thank you very much for taking the time to respond!

I must admit, I am confused. My 3 cube input columns are text types, so inputting a text value such as "202312" should not cause any issues, should it?

Changing the cubes from text type does get rid of the error message, provided they manually enter a date that is in the right format. This, however, is unfortunately insufficient for the requirements. They need to be able to enter only a specific list of months. It's a problem if they can enter any date they wish.

I also don't see how it could be possible to activate suggested values for a date type cube. What would I be comparing it to?

In any case, I am still very confused about why, if I enter info into a text cube from a drop down list, only the first item from the drop down list is accepted, all other values throw an error.

Thank you for the help,

Krisztina

Krisztina Zappert

Hi again Neha,

Upon further testing, I found the issue. I had a selector on the month 202211, and for some reason, even though other months appeared in the drop down list, only this month was accepted.

As soon as I removed the month selection in the screen, all the other months were accepted by the tool as valid inputs.

The cubes remained text types, and the drop down list consisted of month codes.

Thank you,

Krisztina

Neha Hasija

Hi Krisztina,

Yes, this seems to be an issue if its just taking only first value.

Text cube with a cube something like filter cube which will provide the drop-down list/suggested values is working fine but not with just with the entity.

So, workaround is using a cube and meanwhile suggest you to raise the ticket with support.

Thanks,

Neha

Ivano Savogin

Hi Krisztina,

I agree with previous suggestion, can you please setup a simplified case and open it to support? We have some similar issues on Smart Import and I'd like to add this to opened cases. I hope we'll have a fix for it soon.

Thanks and Regards

Ivano
3rd Level Support.

Krisztina Zappert

https://community.board.com/discussion/comment/14476#Comment_14476

Hi Ivano,

Thank you for the interest and the suggestion! A new case has been created! (#00070304)

BR,

Krisztina

Ivano Savogin

https://community.board.com/discussion/comment/14507#Comment_14507

Great news, thanks for the cooperation!

I'll handle it personally and will try to let you have answers ASAP.

Best Regards

Ivano

Ivano Savogin

Just for reference, I'd like to add here the outcomes of the thread separately developed on ticketing platform.

While opening the case, @Krisztina Zappert noted that it was not a problem of suggested values rather than the Smart Import component throws a validation error, if values that are about to be imported do not fall within the active selection.

This is an expected behavior (mainly designed to prevent users that do massive data entry to try to update values outside allowed "pre-defined" bounds).

In the submitted case, even if suggested values were all properly selectable, if the intersection with the perimeter delimited from on screen Selectors was empty, validation error was properly highlighted.

Hope this helps.

Best Regards

Ivano

Krisztina Zappert

https://community.board.com/discussion/comment/14539#Comment_14539

Thank you!