Skip to main content
M
meganm93957598
Participant
March 6, 2018
Question

Naming Recordings

  • March 6, 2018
  • 2 replies
  • 255 views

How does Adobe Connect determine the number appended to an automatically populated recording name?  The app pre-populates the recording name field with the meeting room's name, then appends it with a number.  A faculty member says that his keeps populating with a name that is already used (gets this message: "This name is already in use. Please try a different name."), so he has to manually change the number appending his recording name to the next number.  So, if he chooses Record Meeting and the pop-up populates "Office Hours_130" he can't just enter a description and click OK, because he'll get the "name already in use" error.  He has to actually change the pre-populated name to "Office Hours_131" in order to proceed.  Why is Connect populating a number that has already been used (and thus a name that is already in use)?  How can we get the app to populate the correct number?

This topic has been closed for replies.

2 replies

Jorma_at_Knox
Jorma_at_Knox
Legend
March 6, 2018

Adobe Connect Names the recordings Room Name_X. The X is a numerical value that starts at 0 and counts up from there.

Based on your description it seems that at some point this user renamed his recording with the next highest number from what Connect wanted to name the recording. As a result, the next time he started a recording he received the error message about that name already existing. Since then he has continued to name his recordings 1 number ahead of where Connect wants to name the recordings so the there continues to be a conflict.

Best solution would be to name the next recording something other than the next highest number. Put a letter at the end, 131a for example, or just name it something more specific to what you are recording in the session. This should stop the name conflict loop.

Thomas Gunter-Kremers
Thomas Gunter-Kremers
Participating Frequently
March 6, 2018

I'm not sure how it started but if the database field drives the numbering and he adds one to that number, he might be causing the next time to fail.  If he names one randomly Office_Hours Test and then lets the following recording auto number, it could straighten things out,  It could be that the database ignores what was used last and is just looking at the table entry for that recording and adding a sequential number.  On the programming end, this is a simpler approach.  If he is always adding one to the number, he's just making sure the next one will fail.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices