We use aggrid 15.0.0 with Angular5 (we also have the enterprise license) and I need to use tree data.
I use the example from here (the Organisational Hierarchy example)
https://www.ag-grid.com/archive/15.0.0/javascript-grid-tree-data/#gsc.tab=0
And unfortunately I am not able to see it running in Plunkr, seems like this demo is broken.
My issue is that when I filter by a value that is in the main column no results are returned, this only works for the children values.
This does not work:
This works:
Related
We're really enjoying using the capabilities offered by React-Admin.
We're using <ReferenceArrayInput> to allow filtering of a <List> by Country. The drop-down contains all countries in the database.
But, we'd like it to just contain the countries that relate to the current set of filtered records.
So, in the context of the React-Admin demo, if we've filtered for Returned, then the Customer drop-down would only contain customers who have returned items (see below). This would make a real-difference in finding the records of interest.
Our current plan is to (somehow) handle this in our <DataProvider>. But, is there are more ReactAdmin friendly way of doing this?
So you want to build dependent filters, which is not a native feature of react-admin - and a complex beast to tame.
First, doing so in the dataProvider will not work, because you'll only have the data of the first page of results. A record in a following page may have another value for your array input.
You could implement that logic in a custom Input component instead. This component can wrap the original <ReferenceArrayInput> and read the current ListContext to get the current data and filter value (https://marmelab.com/react-admin/useListContext.html), then alter the array of possible values using the filter prop (https://marmelab.com/react-admin/ReferenceArrayInput.html#filter).
I'm trying to hide the initial (default) first group in a repeatable group, much like what is described in Initially hide first group in Vue-Formulate repeatable group except:
I'm using a schema
My group is a subgroup of another group.
Tried to follow jpschroeder's example and logic here:
https://codesandbox.io/s/vue-formulate-group-with-button-to-start-forked-7u682
The subgroup data is being set to an empty array in the `mounted` lifecycle hook, as recommended, but the field persists...
WAY overthinking this. While I never got the subgroup to not display using the above technique, I think I lost track of the original goal: to just keep the subgroups visualy hidden. If that's the only point, I can include a component in the schema to wrap the group in a details tag:
https://codesandbox.io/s/vue-formulate-group-with-button-to-start-forked-frzd7
While this works, it's a little cluttery. Better to figure out how to replace the div tag in the group template with details, or just use the provided classes to mimic the details behavior.
I want to import elements or members into a GAMS set from other sources, say SQL DB. For example set p plant /p1,p2,p3.../ These elements are successfully imported, however, it seems that they are not ordered, because errors will be reported when I use condition clause like ord(p) > 3 in constraints.
I know that elements are ordered as they initially created. So these imported elements are supposed to follow the sequence as imported. When I display this set, elements are shown as p1, p2, p3...
So I am really confused about the ordering of imported elements. I want to figure out the reason and if there are ways I can fix their order. Thanks.
you could add the following after loading the data
ALIAS(*,universe);
display universe;
$exit;
You should then see the order of your loaded set elements and where the misordering might have appeared. If you absolutely cant order the set in your source query (sql db) a hack would be to initiate a helper set before loading the actual data.
set helper /p1*p100000/;
I have run into a little roadblock in regards to joining mantle entities. I would like to have a single depicting fields from two mantle entities, but am unsuccessful in joining them. Specifically, I have linked a list of party relationships (as contacts) to a single partyId (vendor), with the goal to make a vendor contacts page. However I am unable to link that form-list with the PartyContactMech and ContactMech entities (in order to display email and phone number in the same form-list). More generally, my question is how can one map lists to each other the same way one can map a list to a single object (using entity-find-one and value-field does not work when tried with entity-find)?
There is no need to make a view-entity (join entities) to do that. Simply do a query on the PartyRelationship entity in the main 'actions' part of your screen specifying the toParty (vendor). Then in your Form-List, use 'row-actions' to query the PartyContactMech and so on for each fromPartyId (contact) entry that the previous query returned. Also have a look at the PartyViewEntities file in Mantle USL. There are some helpful view-enties already defined for you there such as PartyToAndRelationship, PartyFromAndRelationship etc. Also note that entity-find-one returns a single "map" (value-field) as it queries on the PK. Whereas entity-find returns a list of maps (list). They are separate query types. If I understand your question correctly.
I looked through documentation and some of the source code too, but am not able to understand the exact use of PaymentGroupMapContainer . I have a sample code - getPaymentGroupMapContainer().addPaymentGroup(ITEM_DESC_GIFT_CARD, giftCard); and in a similar way other payment groups are also added to the container. What if we have multiple gift card, how should this be handled? I am just not able to get the reason why PaymentGroupMapContainer exist
As you've rightly identified, a PaymentGroupMapContainer, can only contain one payment type of type ITEM_DESC_GIFT_CARD. However an order can contain more than one PaymentGroup so to add multiple giftcards to the same order you need to adjust your logic slightly.
First ensure that you create a new PaymentGroup
GiftCard giftCard = (GiftCard) getPaymentGroupManager().createPaymentGroup("giftCard");
Now when you need to apply the giftCard:
getPaymentGroupManager().addPaymentGroupToOrder(order, giftCard);
Obviously there is a lot more to do around getting the GiftCard configured but the above should resolve your original problem about adding multiple GiftCards to a single order.