Changes for page 10 Constraints
Last modified by Artur on 2025/09/10 11:19
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -360,13 +360,12 @@ 360 360 361 361 This may be expressed with the following DataKeySet: 362 362 363 -(% style="width:389.294px" %) 364 -|(% rowspan="3" style="width:89px" %)(% style="color:#2980b9" %)Key1|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ|(% style="width:142px" %)(% style="color:#2980b9" %)M 365 -|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:142px" %)(% style="color:#2980b9" %)DE 366 -|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT|(% style="width:142px" %)(% style="color:#27ae60" %)EUR 367 -|(% rowspan="3" style="width:89px" %)(% style="color:#2980b9" %)Key2|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ|(% style="width:142px" %)(% style="color:#2980b9" %)Q 368 -|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:142px" %)(% style="color:#2980b9" %)MX 369 -|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT|(% style="width:142px" %)(% style="color:#27ae60" %)USD 363 +|(% rowspan="3" %)Key1|FREQ|M 364 +|VIS_CTY|DE 365 +|UNIT|EUR 366 +|(% rowspan="3" %)Key2|FREQ|Q 367 +|VIS_CTY|MX 368 +|UNIT|USD 370 370 371 371 **Use Case 5: A Constraint on allowed values for some Dimensions together with some combination of Dimension values** 372 372 ... ... @@ -376,13 +376,12 @@ 376 376 377 377 Considering the above examples, the following CubeRegions would be created: 378 378 379 -(% style="width:449.294px" %) 380 -|(% rowspan="3" style="width:126px" %)(% style="color:#2980b9" %)CubeRegion1|(% style="width:137px" %)(% style="color:#2980b9" %)FREQ|(% style="width:183px" %)(% style="color:#2980b9" %)Q, A 381 -|(% style="width:137px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:183px" %)(% style="color:#2980b9" %)MX, DE 382 -|(% style="width:137px" %)(% style="color:#27ae60" %)OBS_STATUS|(% style="width:183px" %)(% style="color:#27ae60" %)A 383 -|(% rowspan="3" style="width:126px" %)(% style="color:#2980b9" %)CubeRegion2|(% style="width:137px" %)(% style="color:#2980b9" %)FREQ|(% style="width:183px" %)(% style="color:#2980b9" %)M 384 -|(% style="width:137px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:183px" %)(% style="color:#2980b9" %)MX, DE 385 -|(% style="width:137px" %)(% style="color:#27ae60" %)OBS_STATUS|(% style="width:183px" %)(% style="color:#27ae60" %)F 378 +|(% rowspan="3" %)CubeRegion1|FREQ|Q, A 379 +|VIS_CTY|MX, DE 380 +|OBS_STATUS|A 381 +|(% rowspan="3" %)CubeRegion2|FREQ|M 382 +|VIS_CTY|MX, DE 383 +|OBS_STATUS|F 386 386 387 387 The problem with this approach is that according to the business rule for Constraints, only one should be specified per Component. Thus, if a software would perform some conflict resolution would end up with empty sets for FREQ and OBS_STATUS (as they do not share any values). 388 388 ... ... @@ -390,24 +390,21 @@ 390 390 391 391 DSD CubeRegion: 392 392 393 -(% style="width:280.294px" %) 394 -|(% style="width:156px" %)(% style="color:#2980b9" %)FREQ|(% style="width:121px" %)(% style="color:#2980b9" %)M, Q, A 395 -|(% style="width:156px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:121px" %)(% style="color:#2980b9" %)MX, DE 396 -|(% style="width:156px" %)(% style="color:#27ae60" %)OBS_STATUS|(% style="width:121px" %)(% style="color:#27ae60" %)A, F 391 +|FREQ|M, Q, A 392 +|VIS_CTY|MX, DE 393 +|OBS_STATUS|A, F 397 397 398 398 Dataflow1 CubeRegion: 399 399 400 -(% style="width:285.294px" %) 401 -|(% style="width:157px" %)(% style="color:#2980b9" %)FREQ|(% style="width:125px" %)(% style="color:#2980b9" %)Q, A 402 -|(% style="width:157px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:125px" %)(% style="color:#2980b9" %)MX, DE 403 -|(% style="width:157px" %)(% style="color:#27ae60" %)OBS_STATUS|(% style="width:125px" %)(% style="color:#27ae60" %)F 397 +|FREQ|Q, A 398 +|VIS_CTY|MX, DE 399 +|OBS_STATUS|F 404 404 405 405 Dataflow2 CubeRegion: 406 406 407 -(% style="width:288.294px" %) 408 -|(% style="width:159px" %)(% style="color:#2980b9" %)FREQ|(% style="width:126px" %)(% style="color:#2980b9" %)M 409 -|(% style="width:159px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:126px" %)(% style="color:#2980b9" %)MX, DE 410 -|(% style="width:159px" %)(% style="color:#27ae60" %)OBS_STATUS|(% style="width:126px" %)(% style="color:#27ae60" %)A 403 +|FREQ|M 404 +|VIS_CTY|MX, DE 405 +|OBS_STATUS|A 411 411 412 412 **Use case 6: A Constraint on allowed values for some Dimensions combined with allowed values for Measures** 413 413 ... ... @@ -415,15 +415,14 @@ 415 415 416 416 This may be expressed with the following DataKeySet: 417 417 418 -(% style="width:404.294px" %) 419 -|(% rowspan="4" style="width:99px" %)(% style="color:#2980b9" %)Key1|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ|(% style="width:149px" %)(% style="color:#2980b9" %)M 420 -|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:149px" %)(% style="color:#2980b9" %)DE 421 -|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT|(% style="width:149px" %)(% style="color:#27ae60" %)EUR 422 -|(% style="width:153px" %)(% style="color:#e74c3c" %)CHOICE|(% style="width:149px" %)(% style="color:#e74c3c" %)A 423 -|(% rowspan="4" style="width:99px" %)(% style="color:#2980b9" %)Key2|(% style="width:153px" %)(% style="color:#2980b9" %)FREQ|(% style="width:149px" %)(% style="color:#2980b9" %)Q 424 -|(% style="width:153px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:149px" %)(% style="color:#2980b9" %)MX 425 -|(% style="width:153px" %)(% style="color:#27ae60" %)UNIT|(% style="width:149px" %)(% style="color:#27ae60" %)USD 426 -|(% style="width:153px" %)(% style="color:#e74c3c" %)CHOICE|(% style="width:149px" %)(% style="color:#e74c3c" %)B 413 +|(% rowspan="4" %)Key1|FREQ|M 414 +|VIS_CTY|DE 415 +|UNIT|EUR 416 +|CHOICE|A 417 +|(% rowspan="4" %)Key2|FREQ|Q 418 +|VIS_CTY|MX 419 +|UNIT|USD 420 +|CHOICE|B 427 427 428 428 **Use Case 7: A Constraint with wildcards for Codes and removePrefix property** For this example, we assume that the VIS_CTY representation has been prefixed with prefix ‘AREA_’. In this Constraint, we need to remove the prefix. 429 429 ... ... @@ -435,9 +435,8 @@ 435 435 436 436 This may be expressed with the following CubeRegion: 437 437 438 -(% style="width:379.294px" %) 439 -|(% style="width:264px" %)(% style="color:#2980b9" %)FREQ|(% style="width:112px" %)(% style="color:#2980b9" %)M, Q 440 -|(% style="width:264px" %)(% style="color:#2980b9" %)VIS_CTY (removePrefix=’AREA_’)|(% style="width:112px" %)(% style="color:#2980b9" %)M% 432 +|FREQ|M, Q 433 +|VIS_CTY (removePrefix=’AREA_’)|M% 441 441 442 442 **Use Case 8: A Constraint with multilingual support on Attributes** 443 443 ... ... @@ -449,10 +449,9 @@ 449 449 450 450 This may be expressed with the following CubeRegion: 451 451 452 -(% style="width:382.294px" %) 453 -|(% style="width:190px" %)(% style="color:#2980b9" %)FREQ|(% style="width:189px" %)(% style="color:#2980b9" %)M, Q 454 -|(% style="width:190px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:189px" %)(% style="color:#2980b9" %)MX 455 -|(% style="width:190px" %)(% style="color:#27ae60" %)COMMENT (lang=’en’)|(% style="width:189px" %)(% style="color:#27ae60" %)%adjusted% 445 +|FREQ|M, Q 446 +|VIS_CTY|MX 447 +|COMMENT (lang=’en’)|%adjusted% 456 456 457 457 **Use Case 9: A Constraint on allowed values for Dimensions combined with allowed** values for Metadata Attributes R1: Allow monthly and quarterly data 458 458 ... ... @@ -462,7 +462,6 @@ 462 462 463 463 This may be expressed with the following CubeRegion: 464 464 465 -(% style="width:388.294px" %) 466 -|(% style="width:181px" %)(% style="color:#2980b9" %)FREQ|(% style="width:204px" %)(% style="color:#2980b9" %)M, Q 467 -|(% style="width:181px" %)(% style="color:#2980b9" %)VIS_CTY|(% style="width:204px" %)(% style="color:#2980b9" %)MX 468 -|(% style="width:181px" %)(% style="color:#f39c12" %)CONTACT|(% style="width:204px" %)(% style="color:#f39c12" %)John Doe 457 +|FREQ|M, Q 458 +|VIS_CTY|MX 459 +|CONTACT|John Doe