In the ContactInTag object, the reference to ContactTag is actually the property called Tag. I believe if you expand Tag, it should give you the ContactTag reference.
Hmm. I just tested that and I get the same error (also if I try to expand Entity). I wonder if it's because those are columns inherited from the BaseEntityInTag object (which is virtual)? I can expand CreatedBy fine on that object though. Not sure why the error occurs.
For now you should use two select queries, because using the $expand clause with those columns would give you errors. We passed this problem to Core R&D team and got the information that there is some issue in Core logic that causes that thing, so they would fix it in the next versions.
I would suggest to double-check whether you have tested the functionality in the corresponding sections, as mentioned in the Addon notes: "buttons appear only in sections, cards and details with the registry inherited from the basic schemas (BaseSectionV2, BasePageV2 and BaseGridDetailV2 respectively)" and as an option if the installation was successful, try to clear cache and re-login to the system.
If the issue still persists and even re-installing the addon doesn't help, please contact the addon's support team: creatioapps-support@anserem.com
In such case I would advise to perform recommendations provided above (to clear cache and re-login to the system and in case re-install the application) and if the issue persists, contact the addon's support team.
Should you have any further questions, please let us know!
I now how to customize the name saving in entityFile table but is it the way to change dynamically name of word document downloaded from the print button
You can change the parent object for the detail list schema (step 2 in the article) as shown on the below screenshot:
Also, in case the changes are not reflected straight away once all the required steps from the instruction are done, generate a source code and compile a system.
You can change the parent object for the detail list schema (step 2 in the article) as shown on the below screenshot:
Also, in case the changes are not reflected straight away once all the required steps from the instruction are done, generate a source code and compile a system.
Now the interface works but the list is not working propertly
it allow me create records, but when i refresh the page, i can't see my records and the debugger show the error in the pic , but the records are persisted, i've check it in the DataBase,
The error message indicates that there is an issue with a column: it is either incorrectly added to the schema page or is renamed/deleted.
I would suggest to double-check the article and re-add the custom Attachments detail anew following the guidance so this way it will be properly added to the needed section.
In case the issue still persists or occurs with your custom columns added to the detail afterwards, please approach us at support@creatio.com, so we will be able to check the configuration on the instance and find the root cause of the issue.
You can set up a default value for an 'Assignee' column of your object. However, the object should be in the Custom package. You will not be able to set a default value for the base objects. Apart from that, in this particular example, the case assignee will be the save for all the cases.
But we recommend you double-check the business rule. Please feel free to find the information about business rules in our Creatio Academy article.
The boolean field “IsRead” on the ESNNotification object shows whether the message has been read and whether it needs to be read on the counter (the number on the CTI panel).
Please specify if you are trying to get the photo from the contact or post the photo to the contact. It's not clear from the description of the question.
what you need to do is to call /0/odata/SysImage({Id here})/Data endpoint. And Id should be received from the "PhotoId" column value received when calling 0/odata/Contact({{ContactId}}). Here is an example for accounts from my local app:
Best regards,
