I have created 2 practically identical entities in PowerApps. These two entities both have one field each for a calender date, booking type and number field. Though we want the same design for both entities when adding new records, I have created identical forms for both entities including these three fields for each source. The problem is, that even though both entities are almost exactly the same and I use the three fields that are practically identical, the table reference in powerApps is different. For the first source, everything works fine, I can add a formula for the dropdown in the Data Items field in advanced view to "Distinct('Tablename', 'columnname'). And for the card the formula for AllowedValues "DataSourceInfo('Tablename', DataSourceInfo.AllowedValues, "Columnname")" works perfectly. For my other source however, i get the error "Invalid argument type GUID" when adding both of these formulas. The formulas are accepted however, if I change the formulas to "Distinct([@Tablename], 'columnname') and "DataSourceInfo([@Tablename], DataSourceInfo.AllowedValues, "Columnname")". Why is this? And what does it mean when [@] is used for a table name expression? Because the add new records function does not work properly for the second source where I have to set it to [@Tablename].
Se attached pictures.
This might be good for others to know. It seems like something must have happened to the DataField name, the name had somehow been cut off. Somehow the app maneged to update the field in the entity even though the DataField was wrong, however it updated the field with the default value. When correcting the DataField name it works properly to add new records, however I still need to set the formulas with the @Tablename expression. Why does source 2 have to behave like that? I would appreciate if someone could explain it to me. But the app is at least registering new records correctly now. But the question still remains, why 2 almost identical sources has to be set differently in formulas, hopefully someone else have encountered this as well.
Hi @Anonymous .
I'm having the same issue and I've spent many hours trying to find an answer for this behavior. As you mentioned, I had to use the same @Tablename expression to make it work but its very weird as another sources haven't had to use the @ symbol to make the Patch function works.
Do you've any news about this error, bug or whatever it is ?
PS: I'm using entities in CDS
Find your favorite faces from the community presenting at the Power Platform Community Conference!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021