I have just started using array controllers so my experience with them is very limited.
I am getting this warning in XCode 4.1:
Unsupported Configuration Multiple Objects Using Identifier ""
(Identifiers must be unique)
The double quotes are there with nothing inside. I am using an array controller. It appears for every column of my Table View. I have checked the bindings on each column. Each column is bound to a unique identifier [i.e. arrangedObjects.fullName].
Everything seems to work fine and I am thinking I can just ignore it.
Related
What's the right AQL format to include all values for a multi value property field. Neither #<prop name> nor properties.* seem to work.
When running an AQL query and including a property field which contains multiple values the result contains the first value and not a list containing all values
items.find(...).include("*","#distro")
At present, I run one query to generate a list of artifacts and then iterate through the list running a query for each artifacts properties
f'/api/storage/{artifact.repo}/{artifact.path}/{artifact.name}?properties'
Result
...properties {'key': 'distro', 'value': 'Ubuntu'}
Desired Result
...properties {'key': 'distro', 'value': ['Ubuntu', 'CentOS',...]}
I heard back from jfrog support and the problem seems to be that the use of '#propertyname' allows for the collapse of a potentially multi value property into a single value and this blocks the gathering of all properties.
A more efficient approach would be
items.find(...).include("property")
This results in all properties returned in the json payload as it includes the property domain which includes all the properties.
Additionally, by not using # the query doesn't collapse the properties from lists of values to a single value. So, if build_number is a property it becomes ['25'] instead of 25.
When requesting the property domain, be sure to treat each property as a list.
I have a use-case which consist in storing several maps under an attribute. It's the equivalent JSON list:
[
{"tel": "+33123456789", "type": "work"},
{"tel": "+33600000000", "type": "mobile"},
{"tel": "+79001234567", "type": "mobile"}
]
Also, I'd like to have it searchable at the object level. For instance:
- search entries that have a mobile number
- search entries that have a mobile number and whose number starts with the string "+7"
Since Riak doesn't support sets of maps (but only sets of registers), I was wondering if there is a trick to achieve it. So far I've had 2 ideas
Map of maps
The idea is to generate (randomly?) keys for the objects, and store each object of the list in a parent map whose keys are the ones generated for this only purpose to have a key.
It seems to me that it doesn't allow to search the object (maps inside the parent map) because Riak Solr search requires the full path to the attribute. One cannot simply write the following Solr query: phone_numbers.*.tel:+7*. Also composed search (eg. search entries that have a mobile number and whose number starts with the string "+7") seem hard to achieve.
Sets with simulated multi-valued attributes
This solution consists in using a set and insert all the values of the object as a single string, with separators between them. Yes, it's a hack. An attribute value would look like: $tel:+79001234567$type:mobile$ with : as the attribute name-value separator and $ as the attribute separator.
Search could be feasible using the * wildcard (ugly, but still), except the problem with escaping the separators: what if the type attribute includes a :? Are they some separators that are accepted by Riak and would not be acceptable in a string (I'm thinking of control characters)?
In a nutshell
I'm looking for a solution whatever the hackiness of it, as long as it works. Any idea is welcome.
I have an exercise I'm working to complete; previously it was de-batching multiple XML messages from one file into individual files. Then I had to route individual files based on a field value which had been promoted using filters on a port. Now the exercise has evolved into taking a multi record XML file, breaking it down to individual XML records, and routing their output to different folders based on a value in one of the fields. The hurdles are as follow:
I can't promote a repeating field such as the one I have to use to sort the outbound messages
The value of the field is a system.int32; I am sorting on a "equal to or more than 900" and "less than 900" so I need the int type.
Beyond simple "idNUm >= 900" I am in over my head with the necessary expression(s).
I have the basic orchestration design down, I am just lacking the expressions. The node I am looking to validate against is IDNum, and occurs in each record.
UPDATE: Still not working
I put in the following in my expression: IDNumDefined.Customer.IDNum >= 900
and I get "identifier Customer does not exist in "IDNumDefined"; are you missing an assembly reference?" and "unexpected token '>=' "
Ideas? (sorry about not updating question here)
The debatching has to occur using an Envelope and Body schema.
Once you have this figured out, the debatching can occur using a simple XML disassembler. In the body schema you can quick promote your idNum field by associating a PropertySchema with it.
Once this is taken care of, it is easy to use 2 send ports in order to set your filter subscription(s).
We're using BizTalk and A4SWIFT to generate SWIFT FIN MT 103 messages.
When we're outputting to fields that have multiple options (eg. 57a, 57b, 57c, 57d) we should only have a single output (I'm calling this a field token). However, all available options are output, regardless of whether they should be.
Consider field 57, which can have options 57a, 57b, 57c and 57d.
In our testing, we're limiting to 57a and 57d for now.
We have a map from our source XML document/schema, which selects which fields to use and populates the A4SWIFT schema accordingly.
(I've blanked out irrelevant detail in the image)
In the example, we're looking for a string for the BIC ("ABCDEFGHXXX") and populating the A4SWIFT-side for field 57A IF that is true.
For the Name Address (57d), we check the NameAddress/Line1 field for an arbitrary string which we know will evaluate to false.
(The BIC is fictitious)
This works fine, except we also get an empty result for 57D, even though this should have evaluated to false.
:57A:/
ABCDEFGHXXX
:57D:/
We need 57D to not be there. If the condition Functoid returns False, the Value Mapping Functoid still seems to cause a result.
So we're thinking out Functoid selection isn't right. We've tried with Logical Existence, Logical String and String Equal.
How can we suppress unselected fields from appearing in our output SWIFT?
Try linking through a Equal or Not Equal Functoid directly to 57D and/or 57A. That will suppress the entire loop.
I saw this table :
when I program Asp.net and want to display these special html entities , I use Entity Name.
(but both seems to work)
question :
in what scenarios should I use entity number ( and not entity name ) ?
p.s. Ive seen situation in which asp.net doesnt like Entity Number
There is not clear guidance as to when one should use a numeric character reference (say £) over a character entity reference (say £) or vice versa.
So long as a character entity reference is a defined one (you can define your own), you can use it.
The converse is that if it isn't defined, you should use a numeric character reference.
There is no need to use either of them for most characters. Just enter the characters, in UTF-8, or in ISO-8859-1, whichever you are using. If you don’t know how to type a no-break space, for example, and don’t want to learn it, the entity reference and the character reference are equivalent, so use whichever you find less confusing. (The latter is not an entity reference, so “Entity Number” is a misnomer.)
Only for “<” and for “&”, when used as data characters, will you need “escape” notations, and for them, I cannot figure out any reason why you would use character references, instead of the reasonably mnemonic entity references < and &.