Skip to main content
Participating Frequently
May 20, 2021
Question

Missing precedent error

  • May 20, 2021
  • 10 replies
  • 0 views

Hi Team,

When trying to deploy my application from Dev env to non-prod env getting the below error:

The content [id= uuid=_a-0000e58e-c45f-8000-d3f4-680000680000_197245] was not imported because a required precedent is missing: entity [625a4a28-a511-4d5f-8c44-aca78e625125] in data store [id=54556 uuid=_a-0000dabc-5816-8000-048c-680000680000_28727] cannot be found. (APNX-1-4070-004) (APNX-1-4071-006)

When trying to search with the uuid of missing entity in objects section of Dev env, there is no object found. But the object(query rule) which is dependent on this entity is already present in data store. Unable to figure out the issue. Please help.

Regards,

Anandita

10 replies

deepanshua2124
Participating Frequently
May 20, 2021

Check whether the datastore is added in the package, maybe you create a new datastore entity and that's causing the issue.

Participating Frequently
May 20, 2021

Hi deepanshua,

The datastore is added in the package and it is the existing one itself. I have not created new one.

Thanks

deepanshua2124
Participating Frequently
May 20, 2021

In that case, use function getcontentdetailsbyuuid() and see if you can get more details about that missing uuid.

davel001150
Inspiring
May 20, 2021

Could it be related to the fact that query rules are deprecated?  Perhaps time to consider replacing with a query entity?

Participating Frequently
May 20, 2021

Hey, am not sure about that because the version which we are supporting is 18.3 and we use query rules here.
 

davel001150
Inspiring
May 20, 2021

That's not the problem then.  If you haven't upgraded, they're technically not deprecated yet.

peter.lewis
Participating Frequently
May 20, 2021

One tricky thing about this issue - because the error says the entity cannot be found, you won't be able to search for the entity by UUID (because it doesn't exist [emoticon:c4563cd7d5574777a71c318021cbbcc8]). If you go to the query rule, can you try to remove the current entity referenced and add it again? A couple other questions to help troubleshott:

  • Does your query rule work correctly in your development environment? 
  • Does your data store publish successfully?