ContributionsMost RecentMost LikesSolutionsRe: Add date/time field witn API_AddFieldIn the meantime I've figured out that setting a field type to 'timestamp' at creation is also possible (though it's not mentioned in the API reference), so it basically solves my problem :) ------------------------------ Stepan Gurov ------------------------------ Re: Add date/time field witn API_AddFieldWell, since for date/time fields display_timetag works properly,for date type fields it doesn't automatically switch type to date/time when applying the tag via api. Any api calls that can explicitly switch field type to date/time? ------------------------------ Stepan Gurov ------------------------------ Add date/time field witn API_AddFieldI'm tying to figure out how to add a date/time field in the table using api callAPI_AddField. There's no such type mentioned in the official API reference. ------------------------------ Stepan Gurov ------------------------------ Sequence of internal QB interactionsIs there a known sequence of how internal QB interactions being performed? Specifically: Internal app relation evaluation External app relation evaluation Formula evaluation Webhooks execution QB Actions execution QB Automations execution Notification alerts So in case you have particular field in the record being affected or triggering all of listed above, what is the order of evaluation of all steps (and if it's definite and predictable). If anything else is happening under the hood and worth mentioning, would be happy to know. ------------------------------ Stepan Gurov ------------------------------reference field is not editable (replaced by drop-down)I have a reference field in the table 1, which provides look-ups from table 2. For some reason after setting a connection it becomes a drop-down, containing all values from table 2 and it does not allow to make manual inputs to this field. The only option is to "Create new entry in the reference table", which is not what we need. Api calls and import functionality still works, but straight input has been replaced by this drop-down functionality. Is there any way to switch this drop down off and allow user straight inputs? ------------------------------ Stepan Gurov ------------------------------ Re: Make a field with broken relation editableFrankly speaking, this is the only option came to my mind so far, but I would like to check any options to keep original field open for inputs to stay transparent. And this blocking issue is pretty odd for me, since I've expected to have an easy way to "untangle" any field from any relation and turn it to input field with the default behavior. If you have any other ideas how to achieve this, I would be really grateful.Re: Make a field with broken relation editableTo be on the same page: 1. Change type - tried 2. Making formula - tried 3. Copy app - i've made just two new tables and replicated the pattern: so created relation, deleted referenced table -> then reference filed becomes broken and uneditable.Re: Make a field with broken relation editableWell, this is how its look like: Re: Make a field with broken relation editableWell, this is the screen-shot of all field's settings. Should I change something here? Re: Make a field with broken relation editableThe reference field, so this was the field based on which referencing to other table was done.