set_property keep_hierarchy soft

KEEP_HIERARCHY的用法

set_property keep_hierarchy soft

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Lesson 4-4 - Hiding and Disabling Attribute Hierarchies

  • 4 contributors

set_property keep_hierarchy soft

By default, an attribute hierarchy is created for every attribute in a dimension, and each hierarchy is available for dimensioning fact data. This hierarchy consists of an "All" level and a detail level containing all members of the hierarchy. As you have already learned, you can organize attributes into user-defined hierarchies to provide navigation paths in a cube. Under certain circumstances, you may want to disable or hide some attributes and their hierarchies. For example, certain attributes such as social security numbers or national/regional identification numbers, pay rates, birth dates, and login information are not attributes by which users will dimension cube information. Instead, this information is generally only viewed as details of a particular attribute member. You may want to hide these attribute hierarchies, leaving the attributes visible only as member properties of a specific attribute. You may also want to make members of other attributes, such as customer names or postal codes, visible only when they are viewed through a user hierarchy instead of independently through an attribute hierarchy. One reason to do so may be the sheer number of distinct members in the attribute hierarchy. Finally, to improve processing performance, you should disable attribute hierarchies that users will not use for browsing.

The value of the AttributeHierarchyEnabled property determines whether an attribute hierarchy is created. If this property is set to False , the attribute hierarchy is not created and the attribute cannot be used as a level in a user hierarchy; the attribute hierarchy exists as a member property only. However, a disabled attribute hierarchy can still be used to order the members of another attribute. If the value of the AttributeHierarchyEnabled property is set to True , the value of the AttributeHierarchyVisible property determines whether the attribute hierarchy is visible independent of its use in a user-defined hierarchy.

When an attribute hierarchy is enabled, you may want to specify values for the following three additional properties:

IsAggregatable

By default, an (All) level is defined for all attribute hierarchies. To disable the (All) level for an enabled attribute hierarchy, set the value for this property to False .

An attribute that has its IsAggregatable property set to false can only be used as the root of a user-defined hierarchy and must have a default member specified (otherwise, one will be chosen for you by the SQL Server Analysis Services engine).

AttributeHierarchyOrdered

By default, SQL Server Analysis Services orders the members of enabled attribute hierarchies during processing, and then stores the members by the value of the OrderBy property, such as by Name or Key. If you do not care about ordering, you can increase processing performance by setting the value of this property to False .

AttributeHierarchyOptimizedState

By default, SQL Server Analysis Services creates an index for each enabled attribute hierarchy during processing, to improve query performance. If you do not plan to use an attribute hierarchy for browsing, you can increase processing performance by setting the value of this property to NotOptimized . However, if you use a hidden hierarchy as the key attribute for the dimension, creating an index of the attribute members will still improve performance.

These properties do not apply if an attribute hierarchy is disabled.

In the tasks in this topic, you will disable social security numbers and other attributes in the Employee dimension that will not be used for browsing. You will then hide the customer name and postal code attribute hierarchies in the Customer dimension. The large number of attribute members in these hierarchies will make browsing these hierarchies very slow independent of a user hierarchy.

Setting Attribute Hierarchy Properties in the Employee Dimension

Switch to Dimension Designer for the Employee dimension, and then click the Browser tab.

Verify that the following attribute hierarchies appear in the Hierarchy list:

Manager SSN

Switch to the Dimension Structure tab, and then select the following attributes in the Attributes pane. You can select multiple measures by clicking each while holding down the CTRL key:

In the Properties window, set the value of the AttributeHierarchyEnabled property to False for the selected attributes.

Notice in the Attributes pane that the icon for each attribute has changed to indicate that the attribute is not enabled.

The following image shows the AttributeHierarchyEnabled property set to False for the selected attributes.

AttributeHierarchyEnabled property set to False

On the Build menu, click Deploy Analysis Services Tutorial .

When processing has successfully completed, switch to the Browser tab, click Reconnect , and then try to browse the modified attribute hierarchies.

Notice that the members of the modified attributes are not available for browsing as attribute hierarchies in the Hierarchy list. If you try to add one of the disabled attribute hierarchies as a level in a user hierarchy, you will receive an error notifying you that the attribute hierarchy must be enabled to participate in a user-defined hierarchy.

Setting Attribute Hierarchy Properties in the Customer Dimension

Switch to Dimension Designer for the Customer dimension, and then click the Browser tab.

Postal Code

Switch to the Dimension Structure tab, and then select the following attributes in the Attributes pane by using the CTRL key to select multiple attributes at the same time:

In the Properties window, set the value of the AttributeHierarchyVisible property to False for the selected attributes.

Because the members of these attribute hierarchies will be used for dimensioning fact data, ordering and optimizing the members of these attribute hierarchies will improve performance. Therefore, the properties of these attributes should not be changed.

The following image shows the AttributeHierarchyVisible property set to False.

AttributeHierarchyVisible property set to False

Drag the Postal Code attribute from the Attributes pane into the Customer Geography user hierarchy in the Hierarchies and Levels pane, immediately under the City level.

Notice that a hidden attribute can still become a level in a user hierarchy.

When deployment has successfully completed, switch to the Browser tab for the Customer dimension, and then click Reconnect .

Try to select either of the modified attribute hierarchies from the Hierarchy list.

Notice that neither of the modified attribute hierarchies appears in the Hierarchy list.

In the Hierarchy list, select Customer Geography , and then browse each level in the browser pane.

Notice that the hidden levels, Postal Code and Full Name , are visible in the user-defined hierarchy.

Next Task in Lesson

Sorting Attribute Members Based on a Secondary Attribute

Was this page helpful?

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources

KEEP_HIERARCHY - 2023.2 English

Vivado design suite properties reference guide (ug912).

KEEP_HIERARCHY directs the tool to retain a user hierarchy so that optimization does not occur across its boundary. While this can assist floorplanning, analysis, and debugging, it can inhibit optimization, resulting in a larger, slower design.

KEEP_HIERARCHY is used to prevent optimizations along the hierarchy boundaries. The Vivado synthesis tool attempts to keep the same general hierarchies specified in the RTL, but to improve quality of results (QoR), it can flatten or modify them.

If KEEP_HIERARCHY is placed on the instance, the synthesis tool keeps the boundary on that level static. This can affect QoR and also should not be used on modules that describe the control logic of 3-state outputs and I/O buffers. The KEEP_HIERARCHY can be placed in the module or architecture level or the instance.

  • TRUE : Preserves the hierarchy by not allowing optimization across the hierarchy boundary.
  • FALSE : Allows optimization across the hierarchy (default).

Place the Verilog attribute immediately before the user hierarchy instantiation:

Verilog Syntax Example:

On Instance:

Declare the VHDL attribute as follows:

Specify the VHDL attribute as follows:

Where name is the instance name of a user defined instance.

VHDL Syntax Example:

On a module:

On an instance:

Where instance_name is a hierarchical module.

XDC Syntax Example:

Affected Steps

Select Your Language

Infrastructure and management.

  • Red Hat Enterprise Linux
  • Red Hat Satellite
  • Red Hat Subscription Management
  • Red Hat Insights
  • Red Hat Ansible Automation Platform

Cloud Computing

  • Red Hat OpenShift
  • Red Hat OpenStack Platform
  • Red Hat OpenShift Container Platform
  • Red Hat OpenShift Data Science
  • Red Hat OpenShift Dedicated
  • Red Hat Advanced Cluster Security for Kubernetes
  • Red Hat Advanced Cluster Management for Kubernetes
  • Red Hat Quay
  • OpenShift Dev Spaces
  • Red Hat OpenShift Service on AWS
  • Red Hat Gluster Storage
  • Red Hat Hyperconverged Infrastructure
  • Red Hat Ceph Storage
  • Red Hat OpenShift Data Foundation
  • Red Hat Runtimes
  • Red Hat JBoss Enterprise Application Platform
  • Red Hat Data Grid
  • Red Hat JBoss Web Server
  • Red Hat Single Sign On
  • Red Hat support for Spring Boot
  • Red Hat build of Node.js
  • Red Hat build of Quarkus

Integration and Automation

  • Red Hat Application Foundations
  • Red Hat Fuse
  • Red Hat AMQ
  • Red Hat 3scale API Management
  • Single-page

Language and Page Formatting Options

Red hat training.

A Red Hat training course is available for Red Hat Enterprise Linux

2.3. Modifying Control Groups

2.3.1. setting parameters from the command-line interface.

Example 2.2. Using systemctl set-property

2.3.2. Modifying Unit Files

Managing cpu.

Example 2.3. Limiting CPU Consumption of a Unit

Example 2.4. Using CPUQuota

Managing Memory

Example 2.5. Limiting Memory Consumption of a Unit

Managing Block IO

Example 2.6. Limiting Block IO of a Unit

Managing Other System Resources

Example 2.7. Configuring Cgroup Options

Success! Subscription added.

Success! Subscription removed.

Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile .

  • Intel Community
  • Product Support Forums
  • Intel® Quartus® Prime Software

Quartus Prime Lite keep hierarchy

  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Printer Friendly Page

Christian_Woznik

  • Mark as New
  • Report Inappropriate Content

sstrell

View solution in original post

  • All forum topics
  • Previous topic

Link Copied

SyafieqS

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here .

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice .

  • ©Intel Corporation
  • Terms of Use
  • *Trademarks
  • Supply Chain Transparency

set_property keep_hierarchy soft

Specifying Hierarchical Properties

To set a property of your choice to use an object-based hierarchy, do the following steps:

  • Open M-Files Admin .
  • In the left-side tree view, expand an M-Files server connection.
  • Expand Document Vaults .
  • Expand a vault.
  • Select Configurations and expand Advanced Vault Settings .
  • Expand the Configuration node and select Real Object Type Hierarchies .
  • Select the Hierarchies  > Add Hierarchy .
  • Click Save .

set_property keep_hierarchy soft

Varela_systems (Member) asked a question.

[common 17-69] command failed: unmatched open brace in list

please healp me , i'm trying to get the xsa file . 

  • Vitis Embedded Development & SDK

set_property keep_hierarchy soft

hongh (AMD)

Please check the log after executing the command and provide the actual command and it's output message.

Varela_systems (Member)

  • I don't understand when you say "check the log after executing the command and provide the actual command and it's output message"

When I try to generate xsa file i get un " [common 17-69] command failed: unmatched open brace in list " what can I do for ge succes ?

the log is that :

*** Running vivado

  with args -log design_1_wrapper.vds -m64 -product Vivado -mode batch -messageDb vivado.pb -notrace -source design_1_wrapper.tcl

****** Vivado v2020.2 (64-bit)

 **** SW Build 3064766 on Wed Nov 18 09:12:45 MST 2020

 **** IP Build 3064653 on Wed Nov 18 14:17:31 MST 2020

  ** Copyright 1986-2020 Xilinx, Inc. All Rights Reserved.

source design_1_wrapper.tcl -notrace

WARNING: [Common 17-1361] You have specified a new message control rule that is equivalent to an existing rule with attributes ' -id {Common 17-83} -string {{INFO: [Common 17-83] Releasing license: Implementation}} -suppress '. The existing rule will be replaced.

WARNING: [Common 17-1361] You have specified a new message control rule that is equivalent to an existing rule with attributes ' -id {DRC 23-27} -string {{INFO: [DRC 23-27] Running DRC with 2 threads}} -suppress '. The existing rule will be replaced.

WARNING: [Common 17-1361] You have specified a new message control rule that is equivalent to an existing rule with attributes ' -id {Timing 38-35} -string {{INFO: [Timing 38-35] Done setting XDC timing constraints.}} -suppress '. The existing rule will be replaced.

WARNING: [Common 17-1361] You have specified a new message control rule that is equivalent to an existing rule with attributes ' -id {Vivado_Tcl 4-1062} -string {{INFO: [Vivado_Tcl 4-1062] Incremental flow is disabled. No incremental reuse Info to report.}} -suppress '. The existing rule will be replaced.

WARNING: [Common 17-1361] You have specified a new message control rule that is equivalent to an existing rule with attributes ' -id {Timing 38-91} -string {{INFO: [Timing 38-91] UpdateTimingParams: Speed grade: -1, Delay Type: min_max.}} -suppress '. The existing rule will be replaced.

WARNING: [Common 17-1361] You have specified a new message control rule that is equivalent to an existing rule with attributes ' -id {Timing 38-191} -string {{INFO: [Timing 38-191] Multithreading enabled for timing update using a maximum of 2 CPUs}} -suppress '. The existing rule will be replaced.

CRITICAL WARNING: [Common 17-1355] You are suppressing all messages of type 'WARNING'. You may potentially disregard important DRC, CDC, and implementation messages that can negatively impact your design. If this is not desired, please run 'reset_msg_config -suppress -severity {WARNING}' to undo this change.

CRITICAL WARNING: [Common 17-1355] You are suppressing all messages of type 'CRITICAL WARNING'. You may potentially disregard important DRC, CDC, and implementation messages that can negatively impact your design. If this is not desired, please run 'reset_msg_config -suppress -severity {CRITICAL WARNING}' to undo this change.

---------------------------------------------------------------------------------

Starting RTL Elaboration : Time (s): cpu = 00:00:03 ; elapsed = 00:00:04 . Memory (MB): peak = 1196.160 ; gain = 33.328

Finished RTL Elaboration : Time (s): cpu = 00:00:05 ; elapsed = 00:00:06 . Memory (MB): peak = 1278.578 ; gain = 115.746

Finished Handling Custom Attributes : Time (s): cpu = 00:00:05 ; elapsed = 00:00:06 . Memory (MB): peak = 1278.578 ; gain = 115.746

Finished RTL Optimization Phase 1 : Time (s): cpu = 00:00:05 ; elapsed = 00:00:06 . Memory (MB): peak = 1278.578 ; gain = 115.746

Netlist sorting complete. Time (s): cpu = 00:00:00 ; elapsed = 00:00:00.029 . Memory (MB): peak = 1278.578 ; gain = 0.000

Netlist sorting complete. Time (s): cpu = 00:00:00 ; elapsed = 00:00:00.001 . Memory (MB): peak = 1347.926 ; gain = 0.000

Constraint Validation Runtime : Time (s): cpu = 00:00:00 ; elapsed = 00:00:00.012 . Memory (MB): peak = 1347.926 ; gain = 0.000

Finished Constraint Validation : Time (s): cpu = 00:00:12 ; elapsed = 00:00:13 . Memory (MB): peak = 1347.926 ; gain = 185.094

Finished Loading Part and Timing Information : Time (s): cpu = 00:00:12 ; elapsed = 00:00:13 . Memory (MB): peak = 1347.926 ; gain = 185.094

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/processing_system7_0/inst. (constraint file D:/VARELA/RED_HARDWARE/RED_HARDWARE.runs/synth_1/dont_touch.xdc, line 40).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/proc_sys_reset_0/U0. (constraint file D:/VARELA/RED_HARDWARE/RED_HARDWARE.runs/synth_1/dont_touch.xdc, line 43).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/clk_0/U0/clk_wiz_0/inst. (constraint file D:/VARELA/RED_HARDWARE/RED_HARDWARE.runs/synth_1/dont_touch.xdc, line 49).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/processing_system7_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/proc_sys_reset_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/clk_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/clk_0/U0/clk_wiz_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/adc_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/dac_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/RESET. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/clk_div_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/Signal_Generate_0. (constraint file auto generated constraint).

Applied set_property KEEP_HIERARCHY = SOFT for design_1_i/CEMES_IP_SPLIT_MIO_0. (constraint file auto generated constraint).

Finished applying 'set_property' XDC Constraints : Time (s): cpu = 00:00:12 ; elapsed = 00:00:13 . Memory (MB): peak = 1347.926 ; gain = 185.094

Finished RTL Optimization Phase 2 : Time (s): cpu = 00:00:13 ; elapsed = 00:00:15 . Memory (MB): peak = 1347.926 ; gain = 185.094

Finished Cross Boundary and Area Optimization : Time (s): cpu = 00:00:19 ; elapsed = 00:00:21 . Memory (MB): peak = 1347.926 ; gain = 185.094

Start ROM, RAM, DSP, Shift Register and Retiming Reporting

It's the synthesis report which cannot be helpful for the issue.

Please try to check the log of executed the command in TCL CONSOLE.

Ex: write_hw_platform -fixed -force ...

Related Questions

Community Feedback?

IMAGES

  1. Set Hierarchy Diagram : Infographics

    set_property keep_hierarchy soft

  2. PPT

    set_property keep_hierarchy soft

  3. Property hierarchy with examples of different detailed view modes

    set_property keep_hierarchy soft

  4. 10: The principle of the property hierarchy. Part a) shows an example

    set_property keep_hierarchy soft

  5. Housekeeping hierarchy chart. Hierarchy of Housekeeping in small

    set_property keep_hierarchy soft

  6. Real Estate Management Hierarchy

    set_property keep_hierarchy soft

VIDEO

  1. Check Out Our Most Effective Mail Piece for Our Clients!

  2. The Secret to PROFITABLE Rental Properties! 🤑

  3. #31 User show old value when editing or update a form

  4. How I can Change Default Category Set

  5. #10 AMC Edit old value select, Update and Soft Delete

  6. How to keep buying property when DTI’s come in 2024⎜Property Live

COMMENTS

  1. Removing KEEP_HIERARCHY = SOFT (auto generated constraint) from Xilinx

    July 1, 2021 at 8:22 AM Removing KEEP_HIERARCHY = SOFT (auto generated constraint) from Xilinx Memory IPs During synthesis, the gated clock conversion is not possible on IP module interfaces as auto generated constraint KEEP_HIERARCHY = SOFT is applied to IPs. This is a FPGA emulation project of 3M gate ASIC design and Vivado version is 2020.2.

  2. KEEP_HIERARCHY的用法

    KEEP_HIERARCHY 是一种对综合和实现过程的约束。 一般而言,一个 HDL设计的顶层包含好几个底层子模块。 XST在综合过程中为了得到更好的结果,一般打平设计的层次。 但是也可以在综合的过程中通过添加KEEP_HIERARCHY约束来使综合的过程保持设计的层次。 添加 KEEP_HIERARCHY约束后,综合和实现的结果表现的以下2方面: 1 在实现的过程中保持设计层次。 2 生成仿真需要的保持设计层次的网表。 例子:以上图为例,如果对整个模块或 I2添加约束: 1 在最后的生成网表中,I2模块的层次被保持下来。 2 I2 模块中的I4 、I5模块的层次被打平。 3 I1 、I3 、I6、 I7的层次也被打平。

  3. What are the useful attributes that can be used with passes in Yosys?

    1 Answer Sorted by: 1 The README File contains a list of the most prominent attributes. (Section "Verilog Attributes and non-standard features".) Regarding keep_hierarchy and setattr: Consider the following example code. module test(input A, B, output X, Y); test_and and_inst (.A(A), .B(B), .O(X)); test_xor xor_inst (.A(A), .B(B), .O(Y)); endmodule

  4. Xilinx .ucf documentation

    KEEP_HIERARCHY (Keep Hierarchy) is a synthesis and implementation constraint. If hierarchy is maintained during synthesis, the implementation software uses KEEP_HIERARCHY to preserve the hierarchy throughout the implementation process and allow a simulation netlist to be created with the desired hierarchy.

  5. PDF Top 5 Timing Closure Techniques

    Top 5 Timing Closure Techniques Greg Daughtry Correct Timing Constraints Analyze Before Doing Implementation Strategies and Directives Congestion and Complexity Advanced Physical Optimization Create Good Timing Constraints Create constraints: Four key steps Create clocks Define clocks interactions Baseline Constraints 3. Set input and output delays

  6. Constraints Guide

    If hierarchy is maintained during Synthesis, the Implementation tools will use this constraint to preserve the hierarchy throughout the implementation process and allow a simulation netlist to be created with the desired hierarchy. XST may flatten the design to get better results by optimizing entity or module boundaries. You can set KEEP ...

  7. PDF Vivado Design Suite Properties Reference Guide (UG912)

    Vivado Properties Reference 2 UG912 (v2022.1) June 8, 2022 www.xilinx.com Table of Contents Chapter 1: Vivado Design Suite First Class Objects Navigating Content by ...

  8. Hiding and Disabling Attribute Hierarchies

    An attribute that has its IsAggregatable property set to false can only be used as the root of a user-defined hierarchy and must have a default member specified (otherwise, one will be chosen for you by the SQL Server Analysis Services engine). AttributeHierarchyOrdered

  9. Floorplanning Tips

    set_property IS_SOFT FALSE [get_pblocks slr2_3] add_cells_to_pblock slr2_3 [set pb_cells [all_registers -clock <clock_name> ]] One caveat to this approach is that designers need to remember that dual port BRAMs/URAMs have two clocks. As such, the all_registers command will collect memories where the clock is connected to either of the clock inputs.

  10. PDF Xilinx Constraints Guide

    Constraints Guide www.xilinx.com 3 10.1 R Preface About This Guide The Xilinx® Constraints Guide describes constraints and attributes that can be attached to designs for Xilinx FPGA and CPLD devices. This chapter contains the following sections:

  11. AMD Adaptive Computing Documentation Portal

    Loading Application... // Documentation Portal . Resources Developer Site; Xilinx Wiki; Xilinx Github

  12. 2.3. Modifying Control Groups

    Values higher than 100% indicate that more than one CPU is used. CPUQuota controls the cpu.max attribute on the unified control group hierarchy, and the legacy cpu.cfs_quota_us attribute. Setting the value of the CPUQuota parameter automatically turns CPUAccounting on in the unit file. Users can thus monitor the usage of the processor with the systemd-cgtop command.

  13. Solved: Quartus Prime Lite keep hierarchy

    Quartus Prime Lite keep hierarchy Subscribe Christian_Woznik Novice 08-20-2021 01:45 PM 1,995 Views Solved Jump to solution Hello everyone, I have a design where I would like the fitter to not optimise between the individual modules but do optimise inside. So I can not use the global option for that as that would almost double the resource usage.

  14. PDF Vivado Design Suite User Guide

    -none: Instructs the synthesis tool to never flatten the hierarchy. The output of synthesis has the same hierarchy as the original RTL. -full: Instructs the tool to fully flatten the hierarchy leaving only the top level.-rebuilt: When set, rebuilt allows the synthesis tool to flatten the hierarchy,

  15. Specifying Hierarchical Properties

    To set a property of your choice to use an object-based hierarchy, do the following steps: Open M-Files Admin and go to a vault. Select Configurations and expand Advanced Vault Settings. Expand the Configuration node and select Real Object Type Hierarchies. Select the Hierarchies > Add Hierarchy.

  16. Use of KEEP_HIERARCHY and syn_hier in Vivado

    15 answers 320 views lms_alex (Member) 3 years ago I guess that still doesn't work. That's sad there is no way to tell the compiler to flatten a module when flatten_hierarchy=full. It's either everything or nothing. And Xilinx folks don't seem to understand what you've repeated several times. balkris (Member) 8 years ago

  17. Wix SetProperty if Property does not have a value

    MSI doesn't create properties for the Directory hierarchy in your package until later, in the CostFinalize action. So if you try to set the property before CostFinalize (AppSearch is before this) INSTALLFOLDER doesn't actually have a value. Not totally sure why it updates to [INSTALLFOLDER]servers.cfg and not just servers.cfg -

  18. Bookshelf v8.0: Property Sets and Integration Objects

    The mapping of integration objects, components, and fields to property sets is known as the Integration Object Hierarchy. Using this representation, you can pass a set of integration object instances of a specified type to an EAI business service. You pass the integration object instances as a child property set of the business service method ...

  19. [common 17-69] command failed: unmatched open brace in list please

    Please check the log after executing the command and provide the actual command and it's output message.