Can we suppress BPRule UpgradeMetadataEDTRelation

(0) Share

Report

Posted on by VoltesDev

Hi all,

Just looking for advise. I was create custom table which is the fiels are using EDT from CustAccount, SalesID.

After Build, I got this error

Severity Code Description Project File Line Suppression State
Warning BP Rule: [BPUpgradeMetadataEDTRelation]:EDT relation found in field MyLog of table SalesId. It should be migrated to a regular table relation.

Upon writing, actually just realised, the statement also not correct, the table's name is MyLog, and the fieldname is SalesID.

So, what is this means actually, and can we suppress that? because I don't think I make any relation and don't want to etiher.

Thanks,

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report
Copy link

Link copied!

Why don't you want to make a relation?

It's actually quite important to define the relations properly. And if you don't do it, your relations will break if/when MS removes the existing (legacy) EDT relations.

- Go to main table would not work

- Automatic filtering based on the relation would not work

- If user updates ID of customer or sales order, the ones in your table would not be updated

- Delete actions would not work, possibly resulting to orphan data in your table

Was this reply helpful? Yes No
VoltesDev on at

Like (0)

Report
Copy link

Link copied!

Hi Nikolaos,

So meaning to say, I should go to Sales Table and add relation to my custom table ? also about CustAccount, I should add relation from CustTable ?

..and since this is base table, I should extend those table first then ?

Thanks,

Was this reply helpful? Yes No
Suggested answer

nmaenpaa 101,166 Moderator on at

Like (0)

Report
Copy link

Link copied!

No, you must define relations from your table to CustTable and SalesTable.

If your table has a field that points into another table, then you need to define a relation in your table.

docs.microsoft.com/.../how-to-add-a-relation-to-a-table

Was this reply helpful? Yes No
VoltesDev on at

Like (0)

Report
Copy link

Link copied!

ooh ok.

One more thing, if lets say it is just a log table, which obviously we don't want the information being updated (because of the relation), this is fine to suppress the warning right?

Thanks,

Was this reply helpful? Yes No
Verified answer

nmaenpaa 101,166 Moderator on at

Like (1)

Report
Copy link

Link copied!

You should still define the relation. You also use the relation to control whether the logs should be deleted when the customer is deleted. Or if you want to prevent deletion of the customer if they have logs.

And I would assume that you would want to update the customer account id in the log if your user would update customer account Id. But, it depends on your scenario.

But no matter how you want it to work, you should define relations, and then use the properties of the relations to control the functionality.

Was this reply helpful? Yes No