LosD

I totally agree with @kaspersorensen, but I think we should wait with that until we have a better strategy for it all. Soon we'll (probably) see other changes to configuration...

My guess would be that this is either some wild race condition, or a MetaModel query optimization issue, but we probably need more research first. @kaspersorensen have you ever seen...

With the blackouts, I guess there's confidential information in there, but if you can somehow scrub the execution log for that information, it would help at getting more eyes on...

Yeah okay, not much gained there. Probably better use @kaspersorensen's suggestion.

Yes, it can. It was a preliminary effort to be able to separate OSS and commercial icons. Though I'd recommend instead embracing and using it. The current way is beyond...

I'm not sure about very tedious, but there's certainly work to do.

Should we maybe just use a new output datastream instead? That would pretty much sidestep the issue.

My guess would be that we can escape the table names somehow (like using [tablename] in SQL Server), though that is probably something we need to do in MetaModel.

Doesn't `/PFA/Records/Person@id` work? The row was already selected by the rowXpath, so I would think it should choose the correct one?

(I'm totally green regarding XPath/XML use inside MM/DC though, so it wouldn't surprise me if I was wrong)