When using MIDB, common questions usually involve parameter entry, unexpected results, and suitable text scenarios; this FAQ includes 4 common questions and 4 glossary terms.
FAQ
What should I check first if MIDB returns an error?
- Check whether the parentheses, commas, and field references are complete.
- Confirm that the starting position and extraction byte length are valid values.
- If the referenced field content type does not fit the formula, adjust the source data and calculate again.
Can MIDB be combined with other functions?
- Enter MIDB in the formula field first.
- Use the MIDB result as an argument in another function.
- Save the formula and review record results one by one to confirm the logic.
Why does the result change after I edit the source data?
- Formula fields calculate based on the current record content.
- When the source field value changes, the MIDB result updates as well.
- If you need a stable output for later steps, confirm the source field content first.
What kinds of text is MIDB more suitable for?
- It is suitable for mixed-language text and double-byte character scenarios.
- When character-based extraction does not meet your needs, byte-based extraction is often a better fit.
- Before large-scale use, test with sample records first.
Glossary
| Term | Definition |
|---|---|
| MIDB | A function that extracts a specified part of text by byte count. |
| Formula field | A field type in a multidimensional table that calculates results automatically with a formula. |
| Double-byte character | A character that usually occupies more bytes in byte-based calculations, common in Chinese, Japanese, and Korean text scenarios. |
| Starting position | The parameter that defines where the function begins extracting text. |