I wanted to disable/Remove AddNew button from lookup option in a editable detail.
I could not see any option to edit the settings for the column in the editable detail.
I have attached the screenshot of the lookup in the detail.
Is there any way to set property to disable the option to add New record from the detail column in client schema?
I am able to remove "Add New" if I choose the same object for a lookup field in the form page and by unchecking "Enable adding new values" option in the settings of field. But I am not able to do it for the field in the detail.
Thank you for your question! We double-check the information and found that such an option is yet to be implemented for the mobile schema. We'll register your request to the R&D team to add the functionality in future releases.
As of now, we suggest creating regular detail according to the required conditions.
I've added a custom button in the product in order detail in the order page. But I need to hide this detail custom button when a field, say fieldA, in the order page has the value of 0; and display the detail custom button immediately when user change the value of fieldA to a value greater than 0.
Take it brief, I need to use fieldA as a toggle. When fieldA>0, the detail custom button displays; when fieldA<=0, the detail custom button hides.
We have created a detail and while creating didn’t opt for “Make the list editable” checkbox [didnt check it] and saved it but now not able to select the box and looks like it is locked.
Question : is there a way to check the “Make the list editable” checkbox
Im trying to create a calculated field to show a total of all records from a detail on a record, ive looked into using sql views, however I'm not sure if that would work as you cant filter by the record I don't think, are there any code solutions or anything similar?
You can try creating an integer column in the page (and in the object that this page represents) and create a business process that will change the value in this column once the record is added to the detail (or decrement once the value is removed). This way you can create the logic without additional code that will save resut in the server.
If you still want using the code - something similar is the functionality of the order product detail summary (that displays the number of products in order, can be found on the order page in the "products" tab). This logic can be found in the updateSummary method from the OrderProductDetailV2 from the Order package.
I was having similar issues. What I found out is it depends where the detail is at. For example I was creating a detail around work history.. One of the default fields was contact. If I entered any contact other than the employee I was looking at it wont show on that contact record. There is a logical dependency there... I took the contact component out and works fine.... @Sasori... that is My guess as to what you are running into.
As we connect records to the processes, we would like to display in a detail of the page (e.g. Account) all processes (from Process log) connected to that Account.
I believe that you should be able to achieve your goal by using a [Connect process to object] process element.
With it, you can connect the started process to the Account you want.
First you will need to read out the Id of the record the process should be connected to and then tie it in that element, it should look something like this:
Im trying to replicate this feature the Accounts tab has in its Addresses detail which i'm trying to replicate on a similar detail on a custom section.
Can you see the picture in my post? When you go to enter a new record to the detail it pops up with options from the Address Type field and automatically fills that in with the selected type.
I'm trying too display the same object as 2 separate details filtered by a type, however I want to be able to make each detail auto set that type dependent on which detail was used to add the new record, ive been trying to find a solution but cant, any recomendations?
Please be informed that by the system's logic, the details still refer to the same object and even if you create several different details they are still based on the same object and therefore the edit pages will look the same. We already have this problem registered for our R&D department and in future releases this logic may be changed.
I know they refer to the same object, are you not able to have the different details enter data slightly different? So if you enter it from one detail the type is set to "revenue" and the other "costs", otherwise id need to have a lookup to do it when it shouldn't be necessary.