[ItalianOrgan]

Hi Mike, 

I’d like to suggest an idea that could improve workflows for users who regularly re-import or synchronize their libraries.

1) Import profiles (Batch Import)

I manage my PDF library externally and use another app to access the files. Periodically, I sync my folders with my PC and then re-run imports in MobileSheets.

In Import > Batch Import, I often reuse the same import settings (destination, metadata options, , etc.). It would be very helpful to be able to:

• Save these settings as import profiles
  
• Give them a name
  
• Quickly recall them later instead of reconfiguring everything each time
  

This would make repeated imports faster and less error-prone, especially for users who maintain their library outside of MobileSheets.

I need different import profiles since I manage with collections my Organ Collection, my Choir collection, ...

2) Sync / connection profiles for different networks
A similar need exists for synchronization between devices.
For example:

• At home, I connect using one IP address since I'm connected to Home Wifi.
  
• When I’m outside, I use a different IP or connection setup since I'm connected to Mobile Hotspot.
  

It would be great to:

• Save multiple sync profiles (e.g. “Home”, “Mobile”, “Office”)
  
• Quickly select one without re-entering IP addresses and settings every time
  

Summary
Having reusable profiles for:

• Batch Import settings
  
• Device synchronization settings
  

would significantly improve usability for users with more advanced or multi-device setups.

Thanks for the great work on MobileSheets, and thanks for considering this idea!

[ItalianOrgan]

Hi, since this post got no response at all, I'm just checking in to see if you had a chance to look at the feature suggestion.

No worries if not — I’d just appreciate knowing whether it’s on the radar or if it’s something that won’t be pursued.

Thank you

[Zubersoft]

For any request like this, it's very helpful for me if more users indicate whether they would get any value of it, as it requires a fair amount of work to add all the necessary UI changes and backend changes. If only one user requests something and no one else has requested the same changes, then I'm less likely to incorporate the changes anytime soon (as I typically work on the requests I'm more frequently getting from the most number of users). The only exception to this is if I really like an idea and think it will provide immediate value to many users, or if it's really easy to implement and doesn't require a large amount of work. In this case, your request can be handled by saving off different settings under Settings->Export Settings, and just importing the settings file that matches what you are working with. This changes all of the application settings, so it's a little overkill, but it would get you what you need which is fine if you aren't frequently changing all the application settings. 

Having said that, I'm not completely opposed to the idea keeping a "most recently used" list of IP addresses used for direct connections so that users can quickly choose these. I'm not sure why you are having to manual type in the IP addresses though, as your devices should be able to detect each other automatically on a hotspot. I'm also going to be switching to dnssd, which is a better discovery solution, which might get around any issues you are facing, eliminating the need to type in IP addresses.

Mike

[ItalianOrgan]

Hi Mike,



thank you for your response and the workaround.

I am using a OnePlus 12 and a OnePlus Pad 3.

Discovery is not working, neither via Bluetooth nor via Wi-Fi. In my setup, the tablet is the server and the phone is the client.

For this reason, I am forced to manually type the IP address to establish the connection.

As a possible workaround, could a third option be considered? I.e.: in the popup with manually typing the IP, allow the camera to activate and scan/recognize the IP from the other device (since it is already shown in the server log).
This would make the process much easier and avoid typing errors.