Relative Select commands are very useful for relating one piece of data to another. However, they do not work as intended on some websites. In this article, we'll show you some common errors that may occur with the Relative Select command and how to fix them.
Troubleshooting Data Selection
For this example, I'll be building a project on the FeedSpot blog.
In this example project, we want to extract the name of each blog along with its relative location.
However, when we try to make this Relative Select like normal, every blog name is associated with the location of the first blog instead of their relative locations.
To fix this, first make sure that your Relative Select command is active by clicking on it. Then, click on the name of the second blog to make the Relative Select arrow appears. Now, hold the Shift key, and then click on the location of the second blog. This will correctly train the Relative Select command on the locations for every other blog on this page.
Troubleshooting pagination without a next button
For this example, we are going to use the Home Depot website.
While re-training your Relative Select command when paginating without a next button, a new Relative Select command might be added to your project instead of training the nextPage command correctly. This occurs because ParseHub thinks the button is a completely different element and automatically creates another Relative Select command.
To fix this and add the selection to the current Relative Select command, you can hold the Shift key while clicking on the relative next page. This will add your selection sample to the current Relative Select command instead of creating a new one.