web
You’re offline. This is a read only version of the page.
close
  • Dual Write Setup

    Please allow smooth installation for Dual write orchestration solution. Though we have updated version also facing many errors while installation.
  • Navigating again to the label creation template in visual studio

    When creating the label file in visual studio, we get the summary screen to finalize label creation. After clicking on OK button it is again navigating to the template screen to create label file again. Ideally it should not happen once after creating the label.


    It would be better if you could take this idea into consideration. Thank you.

  • Issue with Positioning of "Empty" Element in BaseEnum Dropdown in UI

    When creating a BaseEnum (for example, a "City" enum to be used in a dropdown), I intend to add an empty element as the first option, allowing the user to make a selection. The process works well when the empty element is created first, followed by other values like "X city," "Y city," and "Z city."

    However, if the empty element is not initially added and I later attempt to insert it after creating "Z city," Visual Studio correctly reflects the new order, but the UI does not update accordingly. The empty element is not positioned at the top as intended, even though it appears in the correct order in Visual Studio. This becomes problematic, especially when dealing with large numbers of BaseEnum elements, as I need to manually remove and re-create the Base Enum if the empty option was forgotten.

    Could you please investigate and address this issue so that the position of the empty element in the BaseEnum dropdown is properly reflected in the UI, even after elements have been added? This fix would be particularly helpful when managing large sets of BaseEnum values.

  • Inconsistent Naming for Form Controls When Adding Form Patterns – "Quick Filter Control" vs. Expected "Quick Filter"

    When adding controls to a form pattern in the designer, most controls follow a consistent naming convention. For example, when adding an ActionPaneControl, the label displayed is Action Pane, and for a GroupControl, the option appears as Group. However, in the case of the QuickFilterControl, the designer displays the full control name—Quick Filter Control—instead of just Quick Filter, which breaks the naming consistency.

    This inconsistency can be confusing, especially for new developers or when working quickly across multiple form patterns. Ideally, Quick Filter Control should be labeled simply as Quick Filter to match the established pattern and improve usability.