Promoted functions fail if the Project name is a prefix of the Library name

Jerome_Pearce

Say we have a Project called MyProject. We then want some lookups, but do not want to keep them in the Project in case we need to change them later. We create a Library called MyProjectLookups. In it we have a class called Lookups with the required functions.

That seems very sensible to me.

When you use any promoted function in that library, the Expression Builder adds something like:

Quote:

Lookups.ListWidgets()

If you rename my Project to MyProject2, and try again, it works, and you get

Quote:

Metastorm.Runtime.Models.MyProjectLookups.Lookups.ListWidgets()

 

which is correct.

If youI have it the first way, every time you use the Expression Builder it gives me a seemingly valid function call that fails on deployment. That causes you to have to add the required prefix in every use. Not fatal, but very, very irritating indeed, especially as some fields seem to 'keep' some reference and still cause errors until you delete the field.

 

Example here:

http://metastorm.processmapping.com.au/post?id=5090441