Requirement:
We are designing report for PM Vibration monitoring scenarion
1. We have multiple measuring points on Equipment Tag
Equipment Tag Measuring Point Document Value
ABC 933 Bearing 1 Horizontal 5
ABC 934 Bearing 1 Vertical 7
ABC 935 Bearing 1 Auxial 3
ABC 1921 Bearing 2 Horizontal 4
ABC 1922 Bearing 2 Vertical 6
ABC 1223 Bearing 2 Auxial 4
and so on (The measuring point are randomly generated numbers, short text is used to identity the bearing and its horizontal, vertical and auxial readings)
2. One Equipment Tag may have max 15 bearings with 03 reading Horizontal, Vertical, Auxial
3. If any equipment have 2 bearing that it will have 06 reading but not necessary the first bearing is bearing 1 and second is bearing 2.. It is also possible that the first bearing on the equipment is bearing no. 3 and the 2 bearing on equipment is bearing no. 4 etc.
4. Our requirement on iview is to display minimum of 1 graph and maximum of 15 graph.
5. Each graph will display 3 values or Series, for Horizontal , Vertical and Auxial values for one single bearing.
6. If we have only 2 bearing for the equipment than we want remaining 13 graphs to be hidden
What we have tried.
1. We have designed a query keeping date of reading and 3 restricted key figures one for horizontal second for vertical and third for auxial values.
2. On visual composer we have called the query 15 times for each graph and passed values using input parameter form.
(We are not using filter in Visual composer bcoz we are not keeping the Measuring point in characteristics. If we try to keep the measuring point in characteristics than horizontal values for each date keeping vertical and auxial values to 0, than vertical values are displayed keeping horizontal and auxial values to 0 and so on.
Problem:
1. We are using input form assign value field to pass the values for measuring points after checking equipment tag,
2. Nested If condition is used to check the equipment and its measuring points.
When the nested conditions are increased, we are receiving compilation error on Visual composer.
3. If fewer nested If conditions are used the model runs/deployed successfully and is working. If number of If condition increased compilation error is received.
4. Flex2Compiler.Compile: FlexCompilerException: Encountered invalid enumerator StaticEnum: null
on compiling again
5. Flex2Compiler.Compile: FlexCompilerException: Encountered invalid enumerator StaticEnum: Encountered "<EOF>" at line 1, column 34.
Was expecting one of:
"ACONS" ...
"ASIN" ...
"ATAN" ...
"ATAN2" ...
"(" ...
")" ...
"," ... etc is received
6. If we compile it again the model is stuck up at 85%
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.