Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Jira Assets - Can't import new objects

Hi All,

I am attempting to create a number of new objects via the import function under an existing object type on JSM cloud. However when I attempt the import, I am given the following error message:

 

150 error(s) found in source data
  • Error: At least one value must be set. [Object (Label: 1, Id: Unknown)].
  • Error: At least one value must be set. [Object (Label: 2, Id: Unknown)].

This continues for the other 148 entries.

The data import sets a couple of fields, with "Name" being the identifier and label. Id is not a field configured in the object attributes or source data, so I assume it is the system field ID (which is the numerical part of the key generated when a new item is created)

I have automation set up to rename the objects based on the key post creation, hence the non-descriptive label. This import in this exact configuration worked ~ 1 week ago, so I am not sure what changed.

Any tips I can try would be appreciated!

 

Thank you,

 

Ryan

1 answer

1 accepted

Welp, I figured it out almost immediately after posting. There was an attribute I was using on the object type that had a minimum cardinality of 1 that I did not specify in the source file. Changing the minimum cardinality to 0 (as that data is no longer required) fixed the problem, as I imagine adding the data to the source file would have.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events