I was wondering if one can mark text fields with schema.org microdata for fields which will contain values retrieved from a database, but which are initially empty upon loading the web page. Basically, I have some fields that I would like to mark using microdata, which will not contain any data until the values are retrieved from a database, the population of which would be initiated by users.
The microdata format is about making data machine-readable.
You 'could' mark up the text fields but I'm not sure why you'd want to.
A search engine will only see the empty field which it won't be filling it in, so no help there.
It's possible that a browser could do something with that data after the user has filled it in, but I can't imagine what.
If your form is saved and presented on another page, then that page is a perfect candidate for microdata markup.
Related
How do I display the value from a relational page link into another text field?
I am creating a Family Tree website for my family. I have set up advanced custom fields where they enter information about their ancestors. To make their experience easier, I am trying to have certain fields populate automatically. For example, if they select their grandmother's name from a relational page link, (each person has their own post created for them), I would then like the value from their relational link selection to appear in real-time in a separate text field, visually. This text field is only there to be used as a label of sorts to indicate where to add the great-grandparent's names. Because as you go deeper into the generations it can get difficult to know where you are at. Having this functionality will orient them quickly as to where to go next.
If this relation link value could populate the Name/Label of the text field that would even be better but I thought that might not be possible.
The scenario is like this: we have a news website, every page display different type of news nodes. We like to set the in this way that, for a single page, no news node should be display more twice. i.e. should not be duplicate.
We are creating paragraphs, which are fetching different type of news nodes based on taxonomies. For a single page, user can add as many paragraph as they want. Each paragraph display nodes with different layout. Paragraph fetching nodes by entity query and views as well.
So question is, how we can restrict nodes, so that if one displaying in one paragraph, it should not display in another paragraph for a single page?
Something like, if we can create a singleton class or static function, so on page load, it create a blank array, and each subsequent call of that function will fill the array and compare with the old list which are already dumped or added. But I am not sure which hook should be used for page load and how to handle the views query.
Beside this should be session specific and also keep it mind about the performance.
Does anyone has any idea on this? Surely its complex.
I have a merchant application form that I want to split up into multiple regions so that the user only has to see one section of the application at a time. Each region is tied to the same table therefore:
Each region would have to share the same primary key
I only want one submission of the form items at the end of the form
I read this post Create an Apex form with multiple pages
which makes it seem like an easy to do process by using the Hide and Show Region template and manually separate the form into multiple regions. The problem I'm running into is that Apex requires a primary key to be tied to each form region, but you also can not have duplicate items on the same page. Any ideas?
-- attaching the PNG of the error message here Primary Key ERR
To me, it looks like a single page with several regions. Doing so, you'd have only one primary key item.
Logically, you'd separate items into different regions. Each of them should use its "Server side condition" which would decide whether to render (i.e. display) that region at certain time or not. It means that it doesn't have to be a hide and show region (besides, it is always here and visible, user just decides whether to reveal its contents or not). You'd create any region type (even an ordinary HTML region).
For example:
the first region displays customer ID, name and address. Other regions are "hidden" because e.g. P1_ID IS NULL is met as no data has been submitted yet. Once user enters ID, name and address and submits the page, P1_ID gets its value which enables other region(s) to be displayed
the second region contains items about some other customer's data; it is now visible because P1_ID is no longer NULL, but 3rd region is still hidden as you didn't enter some required data in the 2nd region which would let the 3rd region to be displayed.
and so forth
Note that the post you are referring to is 6 years old. That is like medieval in apex terms - so much has changed since then.
This is a way to do it if you want multiple pages. Just create multiple pages with the same form (using the create form functionality) and depending on the functionality needed on a specific page you delete the page items you don't want to show. If a database column is not included in the form it will not be touched by the dml process. This should be relatively simple to create.
Note: if you want to get up to speed on forms, read this blog
I am currently working on a project in ServiceNow that requires me to configure around 500 descendants of the Configuration Item table by adding multiple form sections to the CI's with around 10-20 fields in each of these form sections. I currently am doing this by going into the Form Design for each CI, and manually adding these form section and fields for every CI individually, which takes far to long to do for 500 CI's.
Is there a way to add a form section to multiple CI's without having to go into the form design on every CI you want to change and adding it manually?
Technical answer: yes, because all of that form layout data is stored in tables (sys_ui_form_section, sys_ui_section, sys_ui_element, etc) that you could script to insert relevant records. However, due to the complexity (form sections, form elements, ordering) and the potential to run into conflicts (forms differ between tables), I would recommend this only as a last resort.
I think the real question is why is it required to have all of those fields displayed on the forms? If you're populating data from Discovery or a large import, can those fields just be visible by a list page, or just be available to use in filters? Will users actually be clicking to view a CI record and need to see that data on the form? The other part to consider is which view you are adding all of these form sections and fields to. As an example, a user won't see the data on a reference field hover if you're only making changes to the Default view, and won't see any of the fields on a mobile device if you don't add to the Mobile view.
I have a Model that contains some string fields and a List. In the view I use EditFor for the fields, and want to use WebGrid for the List.
Display works fine. But then I use jQuery client-side to let the user add rows to the table generated by the webgrid, which also show up fine on the UI.
However these rows don't appear to be tied back to my model's List upon a submit. In the controller I see that the posted model's string fields contain whatever was entered by the user. But the model's List is empty - it doesn't contain the original values nor the newly added values.
How can I cause the model posted back to the controller to be fully populated, including whatever the webgrid-generated table looks like now, just like fields are?
I see several other questions like this for webgrid on the forum, but none with an answer.
I suppose you are comming from WebForms world. Well this is different in MVC. Here you are back to plain old html and its input fields. No viewstate to hold your rows. Check this link: http://haacked.com/archive/2008/10/23/model-binding-to-a-list.aspx.
Basically you need have consecutive index (or ID) for each row.