Skip to main content

I have a validation business rule that ensures a warehouse code is entered when the status changes from “COMPLETED-REVIEW” to “COMPLETED”.
 

It usually works with a single line code , but when there are multiple lines, the behavior becomes inconsistent depending on the placement. Do you have an idea what could be causing this issue?

 

Hey,

 

One way we've tackled this before is by creating a view that pulls in all related records and determines a validation status based on the results.

 

For example:

  • Build a SQL view with the primary source as request, and join it with non_part_usage records of EVAC PROPANE where user_def3 is null. Count the results.
  • Add this view to the request metadata.
  • Update the input parameter to check the “NPU udf3 null count”—if it’s greater than 0, trigger a validation error.

 


Hey,

 

One way we've tackled this before is by creating a view that pulls in all related records and determines a validation status based on the results.

 

For example:

  • Build a SQL view with the primary source as request, and join it with non_part_usage records of EVAC PROPANE where user_def3 is null. Count the results.
  • Add this view to the request metadata.
  • Update the input parameter to check the “NPU udf3 null count”—if it’s greater than 0, trigger a validation error.

 

In what section do you add it to the custom metadata?


Hey,

 

One way we've tackled this before is by creating a view that pulls in all related records and determines a validation status based on the results.

 

For example:

  • Build a SQL view with the primary source as request, and join it with non_part_usage records of EVAC PROPANE where user_def3 is null. Count the results.
  • Add this view to the request metadata.
  • Update the input parameter to check the “NPU udf3 null count”—if it’s greater than 0, trigger a validation error.

 

In what section do you add it to the custom metadata?

Under “Relation Def”, as a “JOIN” relation type - this allows it to be a viable input parameter source on the business rule.
 

Example:

The Join: 

 

Our business rule in relation to above join:
 

 


Reply